Just to clarify (not contradict) what a couple of people said:
On Sun, Dec 01, 2002 at 08:27:53PM -0800, Wayne Johnson wrote:
> You set up a module alias. If
> you have module A and B, both of which use module C, you can define a
> module X with contains modules A and C, and Y which includes B and C.
>
> X -a A C
> Y -a B C
That only works if A, B, and C are all different directories.
Each sandbox directory must be backed by exactly one repository
directory. If you think about the contents of the CVS/Repository
files, you'll see why this must be the case.
But the tree hierarchies and names need not correspond. You can
have sandbox-directory X contain only some of the files from
repo-directory A. CVSROOT/modules can help you to semi-automate
both of those things. The only thing you can't do is mix
together *files* from more than one repo directory.
That is, you can do this:
Sandbox Repo
X/* A/*
X/C/* blah/common/*
Or this:
X/* A/*
X/C/foo.js blah/common/foo.js
(not present) blah/common/bar.js
but not this:
X/foo.js A/foo.js
X/bar.js blah/common/bar.js
On Mon, Dec 02, 2002 at 01:32:12AM -0500, Larry Jones wrote:
> Symbolic links to directories mostly work, although you may run into
> strange problems with some CVS commands. Symbolic links to files
> subvert the CVS locking mechanism and thus should never be used under
> any conditions.
This refers to putting symlinks within the repo, or naming a
symlink in $CVSROOT. Symlinks in sandboxes don't break, exactly
-- but CVS pretty much ignores them, so you have to use some
other tool, e.g. make, to maintain them.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED]
| | /
Just Say No to the "faceless cannonfodder" stereotype.
- http://www.ainurin.net/ (an Orc site)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
