[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Upcoming dynamic CVSADM patch - 1 workspace >1 repositories for each
Re: Upcoming dynamic CVSADM patch - 1 workspace >1 repositories for each file
Wed, 30 Oct 2002 12:00:28 -0500
On Wed, Oct 30, 2002 at 03:05:48PM -0000, Kris Thielemans wrote:
> I maintain a software library, part of which is public domain, part is
> private. [the public parts will soon move to sourceforge; private parts
> must remain in a local repo]
> I thought that one possible solution for this is to have the subdirectories
> use a different CVS archive
> which this patch could presumably do. Right or
> wrong? Or is there a simpler way (that doesn't need the patch)?
The dynamic-CVSADM patch doesn't apply to your situation; it
addresses a different (though somewhat similar-looking) issue.
I'm pretty sure you can get away with stitching together your
sandbox out of directories that are backed by different repo's:
sandbox/ is backed by some directory on Sourceforge
sandbox/private/ is backed by some directory within your local repo
("pretty sure" means that I think I once did that kind of thing,
but can't recall for sure).
If this does indeed work, you can set it up by doing the right
"cvs co" commands in the right places. (But you'll have to do so
by hand, or script it yourself; I imagine that it goes beyond
what you can express in CVSROOT/modules.) After that, CVS
commands should "just work", recursing as usual and hitting the
two repo's as appropriate.
Failing that, you can always stitch the sandbox together using
symlinks instead; but then you'll have to issue twice any CVS
command that's supposed to apply to both the public and private
halves of your sandbox.
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
The acronym for "the powers that be" differs by only one letter
from that for "the pointy-haired boss".