From owner-freebsd-java@FreeBSD.ORG Sun Nov 9 22:34:29 2008 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13E811065686 for ; Sun, 9 Nov 2008 22:34:29 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id B98758FC0A for ; Sun, 9 Nov 2008 22:34:28 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.14.2/8.14.2) with ESMTP id mA9MZoak092460; Sun, 9 Nov 2008 14:35:50 -0800 (PST) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.14.2/8.14.2/Submit) id mA9MZnKq092459; Sun, 9 Nov 2008 14:35:49 -0800 (PST) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Sun, 9 Nov 2008 14:35:49 -0800 From: Greg Lewis To: Andriy Gapon Message-ID: <20081109223549.GA90295@misty.eyesbeyond.com> References: <48C13406.50606@icyb.net.ua> <4914353A.8010304@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4914353A.8010304@icyb.net.ua> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-java@freebsd.org Subject: Re: separate out tzdata port/package X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2008 22:34:29 -0000 On Fri, Nov 07, 2008 at 02:31:54PM +0200, Andriy Gapon wrote: > on 05/09/2008 16:28 Andriy Gapon said the following: > > I haven't looked at the actual code and have not given any deep thought > > to this, so the following might be silly. > > Is it possible to separate java tz data into its own port/package? > > Maybe even shared by all/some JDKs. > > I usually install java from ports and it seems like a waste to rebuild > > the whole jdk just to get an updated tz data. > > Sorry, still no code. > But here's an idea how this suggested port/package would work. > > It would install (at least) tzupdater.jar somewhere in ${LOCALBASE}/lib > or share. > In its install script it would iterate over registered Sun Java VMs > (javavms file) and execute $vm -jar tzupdater.jar -u (or something similar). > jdk* ports would grow a dependency on this new port and would execute > tzupdater.jar as part of their build/install pretty much as they do now. > > The only issue that I see is that checksum for some files in jdk/jre > installations would not be updated when tz files are modified. But I > don't think that this is a show-stopper. > > What do you think? > Thanks! I would certainly like to be able to get away from updating a lot of ports when a new tzupdater comes out. However, breaking the packing list for already installed ports is a show stopper. A possible alternative is to not install zoneinfo files for any of the JDKs but instead create symlinks to a centrally created set of zoneinfo files created by the tzupdater port you're suggesting. Its not actually a problem that you don't have a JDK to run tzupdater with (hint: see the current diablo-jdk16 port and how it handles tzupdater). For extra credit you could use the zoneinfo files from the existing misc/zoneinfo port rather than waiting for Sun to release updated tzupdater releases. I haven't looked into this at all, so there might be some tricks I'm missing. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org