Re: Using Common files across multiple projects

[Sandeep Takhar]

I am kinda new to cvs.  So I may be understating the
problem.

I think that you could just checkout the modules file
and add the path to the end of each alias.  I tried
the "&" trick and it seems that it doesn't understand
aliases.  (aliases keep the full path name).

with aliases, the modules file looks like

alias_name_1  -a path/to/alias/name/one
alias_name_2  -a path/to/alias/name/two

common_stuff  -a path/to/common/stuff
group_stuff   -a path/to/group/stuff
path/to/common/stuff

The last line is the interesting one.

Without aliases, the -a might work.  Keep in mind that
I am kinda new and so may be way off.

- sandeep
--- Thomas Frasher <address@hidden> wrote:
> Hi all,
> 
> I'm trying to change the repository that we are
> using here.
> There are several projects that use some of the same
> files, headers and .cpp
> files.
> 
> Ideally I would like the checkout to get the files
> automatically, whether
> they are in a different repository (i.e. a different
> module) or whether they
> are local.  This will save me many hours explaining
> this.  Also I need to
> put them back to the "home" repository when the
> changes are committed (all
> this without the need to commit me at the end of
> it).
> 
> I'm confused reading the documentation, it seems the
> ampersan commands are
> what is needed here, but I haven't been able to
> figure out how they work.
> Anyone doing this already?
> 
> Thomas
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs