Date: Tue, 18 Nov 2008 13:33:57 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: Greg Lewis <glewis@eyesbeyond.com> Cc: freebsd-java@freebsd.org Subject: Re: separate out tzdata port/package Message-ID: <4922A825.10703@icyb.net.ua> In-Reply-To: <20081109223549.GA90295@misty.eyesbeyond.com> References: <48C13406.50606@icyb.net.ua> <4914353A.8010304@icyb.net.ua> <20081109223549.GA90295@misty.eyesbeyond.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 10/11/2008 00:35 Greg Lewis said the following: > 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. Greg, this is a great idea - tzupdater.jar seems to contain tzdata*.zip file that in turn contains actual "javazi" files. Maybe, having control over source for freebsd javas, we could tweak java to [first] look into /usr/local/share/javazi (or something like that) instead of creating symlinks. > 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. > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4922A825.10703>