Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: Timezones and versions of Java Followup-To: comp.lang.java.programmer Date: Tue, 24 May 2011 14:40:46 +1200 Organization: Geek Central Lines: 15 Message-ID: References: NNTP-Posting-Host: 118-92-95-178.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1306204846 27046 118.92.95.178 (24 May 2011 02:40:46 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Tue, 24 May 2011 02:40:46 +0000 (UTC) User-Agent: KNode/4.4.7 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4509 In message , Daniele Futtorovic wrote: > On 24/05/2011 01:50, Lawrence D'Oliveiro allegedly wrote: > >> Linux has a perfectly serviceable set of timezone files available >> SYSTEMWIDE in /usr/share/zoneinfo; why do subsystems like Java insist on >> carrying around their own, potentially out-of-date and inconsistent >> copies? > > The JRE carries regularly updated timezone info (which can be updated > independently of the JRE) for the purpose of running in environments > that do not sport a perfectly serviceable set of timezone informations. Which is not the case with Linux. Why can it not use zoneinfo when it’s available?