maintaining a public distribution and local enhancements with CVS

[Kris Thielemans]

Hi,

Is there any way in CVS one can achieve the following:

I have a rather large project (C++) for which I want to make most files
publically available, but not all. (For instance, test stuff, or local
configuration files). I'd like to make the 'public' files into a CVS module,
such that I can either give people CVS access to it, or just make a tarball
after a "cvs update  public-module" or so. In addition, I do want to use CVS
to track my own private stuff as well.

I don't think it's straightforward to do this because I'd like to keep some
of the test stuff in the same directory structure as the public files.

I don't think branches can do this. If I'd put my private files on their own
branch, I would have to continually keep track which branch I'm in to see
where my update should go to (was this a public file or a private one?). And
I would have to synchronise private and public branches all the time.

I guess if I wouldn't put files in the same directories, an ampersand-module
for the public stuff would do the trick. Or can I have 2 modules in the same
root-directory ? Any other solutions?

Thanks!


Kris Thielemans
(address@hidden)
Imaging Research Solutions Ltd
Cyclotron Building
Hammersmith Hospital
Du Cane Road
London W12 ONN, United Kingdom

Phone on :   +44 (020)8383 3731
FAX on :     +44 (020)8383 2029

web site address:
http://www.irsl.org/~kris