Date: Sun, 27 Mar 2011 13:31:22 -0700 From: Doug Barton <dougb@FreeBSD.org> To: David Wolfskill <david@catwhisker.org> Cc: hackers@freebsd.org Subject: Re: Keeping /etc/localtime up-to-date Message-ID: <4D8F9E9A.50604@FreeBSD.org> In-Reply-To: <20110327153835.GA87420@albert.catwhisker.org> References: <20110327153835.GA87420@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/27/2011 08:38, David Wolfskill wrote: > It would (in principle) be possible to teach mergemaster(8) how to > do this (possibly by including a cookie in ~/.mergemasterrc or > /etc/mergemaster.rc to tell it what the "reference" zoneinfo pathname > is), but this type of approach seems sufficiently different from > (the bulk of?) what mergemaster does currently that I'm unconvinced > that this is reasonable, let alone ideal. Yeah, I wouldn't be enthusiastic about this. :) > So it seems to me that requirements would be: > * The content of /etc/localtime must provide the appropriate > "zoneinfo" information, even when/usr/share/zoneinfo/* has been > modified (or shortly thereafter, in concert with "make installworld"). This is more along the lines of something that would be easy to work with in mergemaster. If I can tell what file in /usr/share/zoneinfo to compare /etc/localtime to (ideally with fully path), I'm happy to provide a mechanism in mergemaster to make sure it stays up to date. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8F9E9A.50604>