-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wes Hardaker wrote:
|>>>>>On Thu, 01 Jul 2004 14:02:28 +0100, Dave Shield
<[EMAIL PROTECTED]> said:
|
|
| Dave> R 5.1.1
| Dave> C 5.1.1+cvs  2004/06/01
| Dave> R 5.1.2.pre1
| Dave> C 5.1.2.pre1 2004/07/01
|
| I don't think the reported version number as released by the tools
| should have anything other than things parsable by .s.  IE, 5.1.1.cvs
| and 5.1.2.pre1.cvs should be the only style things we use.  The reason
| being is that scripts are written that parse version numbers and
| stuff.  I don't know if any exist, but it wouldn't surprise me.  I've
| written some before, so I'm sure someone else has.
|
| IE: my preference would be to take the current version just released
| and auto-append a .cvs to the end.  For new branches and the main
| line, we should tag it as version.pre0 or version.notyet0 or some
| other tag.
|

I don't see why this needs to be kept in CVS. It should be generated
when you build. Add some code to configure/Makefiles to check if the
build is in a CVS tree, work out the newest Entries line and call
local/Version-Munge.pl to fix up the version strings.

If you include a CVS timestamp in the cryptic seconds-from-the-epoch
format you can keep the "parsable by .s." criterion. e.g.
the above 2004/07/01 would give 5.1.2.1088640000
my CVS would get 5.1.2.1088318449

You can then say to people - "that is fixed in CVS from 5.1.2.1088766622"

- --
There's no point in being grown up if you can't be childish sometimes.
~                -- Dr. Who
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFA5UPDUpRmj8xnsFgRAgMHAJ9OR/M9FqZ2a/I/pJEPjUe6u7jKvACfSbNk
09DTW+5Abhsc+CKqI9y5Lvs=
=KWOz
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to