Date: Sat, 04 Jan 2003 19:46:24 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp-workers AT delorie DOT com Message-Id: <2561-Sat04Jan2003194623+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <20030104163625.GA11214@kendall.sfbr.org> (message from JT Williams on Sat, 4 Jan 2003 10:36:25 -0600) Subject: Re: man pages for djtzn204 References: <20030103164819 DOT GA3056 AT kendall DOT sfbr DOT org> <2593-Sat04Jan2003130317+0200-eliz AT is DOT elta DOT co DOT il> <20030104163625 DOT GA11214 AT kendall DOT sfbr DOT org> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Sat, 4 Jan 2003 10:36:25 -0600 > From: JT Williams > > -: > If so, the makefile might have to be patched every time the timezone > -: > sources are updated > -: > -: Why is that? What am I missing? > > The TZ makefile (zoneinfo/src/makefile) doesn't look like a djgpp makefile. > I assumed it came as part of a TZ distro and would therefore be overwritten > (and require re-patching) whenever the TZ distro was updated. That's true to some extent: zoneinfo/src/makefile was hacked by yours truly to make it work with the libc build procedure. See, for example, the inclusion of makefile.def and the definition of $(UTIL), which were my additions. However, the makefile that comes with the tzcode distro doesn't change much, so in practice one only needs to see that the changes are not significant, and if so, keep the makefile we have on our CVS. In general, I used to import a new version of tzcode/tzdata only a very short time before a new version of DJGPP is about to be distributed. So the maintenance burden is not very high.