> I don't see why this needs to be kept in CVS. It should be generated > when you build.
Just to check - what do you mean by "it" here? The base version tag, the fact that this code tree is a CVS development version, or the precise date it was checked out? The base version needs to come from *somewhere*. And that "somewhere" needs to be in the CVS system, so it can be updated when we make a new release. I can see the attraction of adding a timestamp automatically as part of configuring the software, but this shouldn't touch the source of the base version tag. Otherwise it just takes one moment of inattention from one of the developers when committing a change, and Shield's screwed up the CVS tree yet again :-( It probably doesn't matter too much whether the ".cvs" tag is part of the base version (and updated by hand) or added automatically. But it feels safer (and somewhat simpler) to do it by hand, since that doesn't need any new code. But I'd tend to agree that adding a timestamp (or similar serial number) would probably be better done "outside" CVS. Dave ------------------------------------------------------- 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
