🚀 go-pugleaf

In article <1992Nov2.091110.4435@ericsson.se>, etxmesa@eos.ericsson.se (Michael Salmon) writes:
|> In article <1992Oct29.182305.14061@brtph560.bnr.ca>, 
|> chrisf@brtph316.NoSubdomain.NoDomain (Chris Fulmer) writes:
|> |> In article <1992Oct28.074024.14827@news.tu-graz.ac.at>,
|> |> tab@piis05.joanneum.ac.at (Behnam Tabatabai) writes:
|> |> > Is there a possibility to check out only a subset of files managed by
|> |> > RCS or SCCS by assigning a symbolic names to different subsets? 
|> |> > 
|> |> 
|> |> Yes there is in RCS at least.  Look at the -N and -n
|> |> options to the rcs command.  It's then possible to check
|> |> out a version of a file by specifying its symbolic name.
|> |> 
|> |> The only thing that you'd need to do is make a short shell
|> |> script which looped through all the files, checking out the
|> |> version specified by the symolic name of each file.
|> 
|> The original poster wanted to group files the other way, not by
|> revision but by name, so that if I say co xyz where xyz is a group name
|> then I will get abc, def, and ghi which I previously defined as
|> belonging to xyz. IMHO this is only useful in systems like VMS that
|> don't have make by default.

Yeah.  That was my point.  I was trying to say that you could mark
each node of a specific configuration.  You then make a shell script
which says something along the lines of:

foreach f (RCS/*,v)
co -r $1
end

Call this script "myco", and suddenly you can do a "myco xyz."

------------------------------------------------------
Chris Fulmer                    Bell-Northern Research
Sr. Software Designer            Research Triangle, NC
mail to woodstock!chris@mcnc.org (preferable) or...
        chrisf@bnr.ca            (not so preferable)
Oh yeah.  The usual disclaimers apply here.