Re: Sharing files among projects

[Paul Sander]

Why can't you place the header files in their own module, and include
that module in another one, using either the -a or & operators?

Another method that's used successfully is to create baselines to which
developers create references.  Your symlink method is one way to do it,
but there are others.  One alternative is a publish/subscribe mechanism
called "Buildref" that you can find at http://www.wakawaka.com/source.html .

--- Forwarded mail from address@hidden

Hi there. :) I'm fairly new to cvs from an admin perspective, and I've
got what I hope is a pretty easy question.  We've got a number of
headers files, etc that need to be available for building a number of
different applications.  We need to be able to get all of the header 
files easily without resorting to multiple projects to split the headers 
out, etc.  What I've discovered in playing with some test projects is 
that I can sumlink from the target project to the source project, and it 
seems to work fine.  Make the symlink, update my working directory, and 
vi-ola.  There's the shared file.  My question is this:  Is this a safe 
practice.  Are we going to run into problems later if we follow this 
route?  If it is a safe thing to do, what are the chances of adding this 
funtionality to cvs itself.  If unsafe, how is this problem correctly 
solved?  With so many larege projects, I know this has been solved... 

--- End of forwarded message from address@hidden