Externals don't really match VSS file sharing since they have to be
checked out, committed and updated separately (if I understand them
correctly). My organization went from VSS to SVN. We used VSS shared
files for common code between products. Luckily in our case there
were so few non-shared files (<1%) that we just converted to a single
code base and conditional compilation, removing the need for shared
I'm not aware of a good SVN replacement for VSS shared files.
Tim Hill writes:
> Yes, externals would do it. Since you are at a "cusp" if you switch
> scc systems, I also would advocate cleaning up the way you share
> files -- you are much better off sharing at the folder level than
> individual files here-and-there all over the place. Much more robust.
> On Nov 15, 2006, at 11:28 AM, Steve O'Hara wrote:
> > I'm a newbie to SVN and come from a VSS (I know, I know) background.
> > We'd really like to switch to subversion but the one show-stopper
> > for us
> > is the lack of file sharing.
> > A very large number of our VSS projects share code files. In fact,
> > I'm
> > not sure we have any projects that don't share some sort of file with
> > another project.
> > Now VSS has it's faults, but this feature is a real winner in our
> > developer community and prevents the re-invention of the wheel. In
> > fact, I'd go further and say thay this feature has been fundamental to
> > the increased stability of some of our modules - as they get used in
> > more and more projects they get better and better debugged in more and
> > more diverse operating conditions.
> > As I understand it, the "externals" feature of svn is only
> > applicable to
> > directories. Has anyone got any ideas how I could mitigate the
> > lack of
> > sharing files in svn that might come some way close to exhibiting the
> > desired behaviour?
> > Thanks,
> > Steve
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Nov 15 23:19:41 2006