Re: 'soft links' in cvs repository?

[Paul Sander]

Nope.  RCS files stored in the repository are copied and replaced;  
they are not updated in place.  If a symlink is created to point to  
an RCS file, then the link will be replaced by a modified copy of the  
original RCS file, and the original will also remain.  Remember,  
you're replacing a pointer with an actual copy.

You can get away with creating symlinks in a repository, if they  
point to directories (but not Attic directories).  However, this  
practice is not recommended.

Another approach to mapping individual files to multiple projects is  
to use the modules database.  This solution does not scale well and  
is difficult to maintain.

A better approach, if it is available to you, is to split out the  
common files into a separate project and use build-time references to  
its contents.

On Mar 5, 2008, at 2:34 PM, Frank Petrillo wrote:

> Would using sym-links solve the problem?
>
> File A in repository 1 can have sym-links in repo 2 and 3.
> So whenever you make changes to File A in repo 1 the file is linked to
> repo 2 and 3.
>
> I suppose this would not help if you wanted to have changes made in  
> repo
> 2 or 3 as well.
>
> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden On
> Behalf Of newbie
> Sent: Wednesday, March 05, 2008 8:10 AM
> To: address@hidden
> Subject: 'soft links' in cvs repository?
>
> Hi Group,
>
> Is there any way to use one file in different cvs repositories while
> keep it synced? (just like a soft link to the file).
>
> Let's say I have three files A, B, C. What I want to do is I need to
> put A, B in a repository 1, meanwhile I need to put A, C in another
> repository 2, but file A should be the same here. Whenever I commit
> changes for A from a checkout of repo 1, it should also be changed in
> repo 2. File A in repo 1 is just a soft link to repo 2.
>
> Any hints on this? Hope I was clear.
>
> Thanks.