RE: Migrating from sourcesafe to cvs

[Wouter Brissinck]

Hi,

The reason is purely political : i have to convince people
who have worked for a long time with sourcesafe.  If it envolves
changing the way they work due to CVS being "underfeatured"
it's going to be very hard.  

The reason why we want to migrate is that we are currently 
stuck with Sourcesafe Offsite, which turns out to be hopelessly
unstable (several server crashes a day) over a low quality
internet connection.  I have the feeling that CVS over ssh
will do better.

Regards,

wouter



> Why isn't it feasible to share the files via a shared 
> installation location or a
> library?  Are you able to change your build system to take 
> care of these
> dependencies?
> 
> Noel
> 
> Hello,
> 
> We are considering to migrate our code from MS Sourcesafe to CVS.  One
> problem
> that arises is that we currently have a lot of files which are shared
> between several
> modules.  I.e., a single file is present in several modules, 
> and updating it
> in one module
> causes it to be updated in another.
> 
> In the CVS manual i couldn't find an equivalent mechanism.  
> As moving all
> our shared
> files into libraries is not feasible, i am wondering if there 
> is a way to do
> shared files
> in CVS.
> 
> Regards,
> 
> wouter