In article <a28pfa$1dj6$[EMAIL PROTECTED]>,
Petr Aubrecht <[EMAIL PROTECTED]> wrote:
>The idea was to put $Revision$ into configuration file as a version number
>of the software. Then I have automatically increasing version number (like
This is a good idea if you want the user to be able to identify the
revision of each component (such as using ident or what commands). But not
for identifying the version of the release.
>in Borland C++ Builder). It allows frequent releases and stay sure the user
>has the latest version. I don't like to do it manually (every day).
Borland C++ Builder is a build system. Not an SCM system.
While it may be wise to keep track of the information in CVS, it should be
the build system (be it make or whatever) that assigns identification to
the release.
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
