> -Original Message-
> From: [EMAIL PROTECTED]
> But how do I embed into the files the right version number? I could
> use $Version$ or similar, but this would be the version of the file,
> not the release of the whole project.
$Name$ (oddly enough) is expanded at export time to the valu
On 19 Feb 2001 13:34:02 +0100, [EMAIL PROTECTED] (Kai
Großjohann) wrote:
>Suppose I have a software package which contains of many individual
>files (a Perl module). And suppose I want to make several releases.
>Then I'd make a tag to apply to all files.
>
>But how do I embed into the files the
What you need to do is use the "cvs tag" or "cvs rtag" command to tag the
relevant versions of the four modules with a symbolic tag such as
"release_2_0". You may also want to use the cvsroot/modules file to define
a "module" for your product with all four modules A, B, C, and D in it.
Then "c
might need.
Hope this helps.
- Tim
-Original Message-
From: Marinalva Dias Soares [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 28, 2000 8:52 AM
To: Joerg Beyer
Cc: CVS-II Discussion Mailing List
Subject: Re: Releases!
I have a program that's composed by 4 modules with differents v
CVS is not a build or configuration management tool. It only tracks multiple
versions of source code so it will not help you much.
>From my (limited) experience with the software, the best you will get is to
be able to label source code for a particular release so that you can
extract that versio
I have a program that's composed by 4 modules with differents versions. I
want generate a release 2.0 with versions 1.3.1 of module A, 1.2 of module
B, 1.4.2.1 of module C and D.
cvs export do it? how, please?
thanks, Marinalva.
On Fri, Jul 28, 2000 at 08:02:02AM -0300, Marinalva Dias Soares wrote:
>
> Hello everybody!
>
> Anybody know how can I generate a release of a software with CVS?
is "cvs export" what you want?
Joerg
--
"Nobody will ever need more than 640k RAM!" -- Bill Gates, 1981
"Windows 95 needs
