On 9/6/06, Robert Denton <robert@headsprout.com> wrote:
> 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'?
TortoiseSVN is simply a Subversion client. You probably want to use
svn:externals to link another section of your repository (or a
resource in a whole other repository) to your project. You can only
set svn:externals at a directory level; you can't "share" a single
file into another directory (I think VSS let you do this).
http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html
---------------------------------------------------------------------
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:18:42 2006