setup versioning

[Earnie Boyd]

--- DJ Delorie <dj@delorie.com> 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: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/