[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Best way to handle shared files in SVN?

From: Robert Denton <robert_at_headsprout.com>
Date: 2006-09-06 20:00:02 CEST

Hi all,

Thanks for listening. I am wondering what is advised as to the best
way to handle shared components across multiple projects in SVN.
Here is the situation:

My boss, who has always used VSS before the introduction of SVN on
our network, likes to use shared libraries, etc in his projects and
will have the same file in a number of different locations. In VSS
he could just drag and drop the shared file into new projects and VSS
knew it was 'shared' component and any change made to it would apply
in all instances.

With TortoiseSVN being a shell extention (and thus a different beast
entirely) we are not sure if simply creating a plain old file system
shortcut is sufficient to emulate this behavior. Is there some other
method or property used by Subversion to make a file as 'shared'?

Thanks for any and all input on this issue.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 6 20:02:44 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.