RE: question on co

[Skinner, Gayle R]

Thanks for you suggestion, but I was trying to get away from managing
things outside of the RCS.
I received the following from another user.
It does what was wanted, all within RCS.

I use labels to help me manage my code. For example, when done with a 
release a drop a label on all the code

for all files
do
/usr/local/bin/rcs -n"$LABEL_NAME": $file_name
done

Than you can pull all code by a label regardless of revision

for all files
do
eco -p$LABEL_NAME file > where ever
done

Hope this helps

-----Original Message-----
From: Aaron S. Hawley [mailto:address@hidden
Sent: Thursday, March 18, 2004 1:33 PM
To: Skinner, Gayle R
Cc: address@hidden
Subject: Re: question on co


how are you using co?  like this?:

co -r1.2 *

in man co(1) the -r option says:

"retrieves the latest revision whose number is less than or equal to
rev."

so it will check out a file if it's there whether a version exists or
not.
RCS works on a file-by-file basis, not enforcing any assumptions about
files in a repository like CVS does.

though GNU Make can manage RCS files slightly.  though this would
require
that your files a, b, and c have some target file say t (which maybe it
doesn't, cause you're not compiling anything, though you could have t be
just a phony target file that simply gets modified with `touch`).

for example in a Makefile that you maintain (maybe you already do) that
changes throughout the project that specifies the files-needed for a
certain revision.  thus:

make COFLAGS=-r1.2 t

would check out revision 2 of your project.

with Makefile:

#!/usr/bin/make

$Revision: 1.1 $
t: a b c
        touch $@
## end of Makefile

and then this in revision 1.2:

#!/usr/bin/make

$Revision: 1.2 $
t: a b
        touch $@
## end of Makefile

just a thought.

note that "state" is a keyword in RCS, but I understand what you
meant.

HTH,
/a

On Thu, 18 Mar 2004, Skinner, Gayle R wrote:

> When using co, is there a way to tell the program not to pull a
revision
> (other than by date/owner)?
> For example: Project state at rev 1.1 has three needed files a,b,c.
>               Project state at rev 1.2 doesn't need c anymore. It's
> state is files a,b.
> It would be nice to pull (read-only) the rev 1.2 and not see the file
> (rev 1.1) c.