This is the mail archive of the
mailing list for the Cygwin project.
Re: help/version patches
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-patches at cygwin dot com
- Date: Mon, 25 Feb 2002 00:29:38 -0500
- Subject: Re: help/version patches
- References: <firstname.lastname@example.org>
- Reply-to: cygwin-patches at cygwin dot com
On Sun, Feb 24, 2002 at 09:21:43PM -0800, Joshua Daniel Franklin wrote:
>I've got patches for each of the utils to add/correct the help and
>version output options. There are 13 in all. I incremented the
>version number 0.01 from the ones in CVS/Entries with the
>exception of cygpath. I also added a line based on one found in
>strace that imbeds the compile date into the version output:
> case 'v':
> printf ("cygpath (cygwin) 1.21\n");
> printf ("Path Conversion Utility\n");
> printf ("Copyright 1998-2002 Red Hat, Inc.\n");
> fputs("Compiled "__DATE__"\n", stdout);
> exit (0);
>Please someone let me know if this is a Bad Idea for some reason.
>I would also very much like to know the best way to submit these.
Adding version numbers is not a bad idea (although, I can't honestly
think of a time when it would have helped to have this information).
Adding version numbers in the middle of the program, in the middle of a
text string is, IMO, a bad idea. The version number should be at
the top of the program in a
const char version = "something";
and referenced in the version string.
As Robert indicated, using the CVS version number is probably the best
way to handle this. setup.exe currently uses the CVS version. Use that
as an example.