From owner-freebsd-java@FreeBSD.ORG Fri Nov 7 12:47:52 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 84E64106568A for ; Fri, 7 Nov 2008 12:47:52 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BC3AE8FC46 for ; Fri, 7 Nov 2008 12:47:51 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA09344 for ; Fri, 07 Nov 2008 14:31:54 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4914353A.8010304@icyb.net.ua> Date: Fri, 07 Nov 2008 14:31:54 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20081106) MIME-Version: 1.0 To: freebsd-java@freebsd.org References: <48C13406.50606@icyb.net.ua> In-Reply-To: <48C13406.50606@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: Fri, 07 Nov 2008 12:47:52 -0000 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! -- Andriy Gapon