Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <20000803120930.7207.qmail@web118.yahoomail.com> Date: Thu, 3 Aug 2000 05:09:30 -0700 (PDT) From: Earnie Boyd Subject: Re: setup versioning To: DJ Delorie , cygwin-developers AT sources DOT redhat DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- DJ Delorie wrote: > > I was just thinking that the CVS revision of "ChangeLog" might be a > good automatic version number for setup (aside from the fact that it's > 1.x instead of 2.x, but I can fix that). > IMO, that won't work well. What happens if the ChangeLog is updated more than once between distributions? > Another thought is to auto-tag all the source files, and provide a > dialog that shows them all, for troubleshooting purposes. A grep or > sed could be used to build a .h from all the *.c keywords in their > comments. > > Comments? Perhaps strings similar to what's in the cygwin1.dll would be helpful. Then one could grep for %%% in the executable for build information. Personally I don't see anything wrong with a generated version.c to control versioning information. Cheers, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/