[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nesting packages using CVS

From: Mark E. Hamilton
Subject: Re: nesting packages using CVS
Date: Tue, 18 Apr 2006 09:49:03 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.7.12) Gecko/20050920

Bob Rossi wrote:
Both of these packages are managed using CVS. I need to include package
B into package A in a nice way.

I will make changes to both package B in it's own repository, and I will probably make changes to package B in package A's repository. What's the
best way for me to include package B in package A's repository? Should I
use the import command?

I'd suggest not doing this. You're just going to cause yourself headaches. Either put A and B in a single repository as Sergei suggested, or keep them in separate repositories, but don't duplicate one repository in another. In general you want only one 'true' copy of the repository, which is the only one in which you should ever make changes.

Since you mention autoconf I assume you're talking about including B in A for development purposes. Some time back CVS was modified to allow directories from different repositories to be checked out into a single working directory. As long as you only have directories at the top-level of each repository (and TopLevelAdmin is not set to 'yes' in CVSROOT/config) you should have no problems checking out both A and B in your working directory. You could even check out B in a sub-directory of A, and CVS would correctly traverse the hierarchy.

The only thing you couldn't do is to check out both A and B with a single command. As far as I know there's no was to define a module one repository that actually refers to directories in a different repository. Still, you could write a script that would do it for you.

Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]