You don't say where this need to have the same file 'shared' in different
places comes from; but for any compiled code you could probably refactor
this into a single utility library; this can then be referenced by
other projects.
Where I've used 'sharing' before with VSS was with asp files that
go into more than location for a web site....
With SVN I now have a single copy of the file in the repository, and a
NAnt build script is used to deploy the file to different locations.
Tom
> -----Original Message-----
> From: Scott Palmer [mailto:scott.palmer@2connected.org]
> Sent: 06 October 2004 19:01
> To: Subversion List
> Subject: Re: Sharing files like in MS Visual SouceSafe
>
>
> I don't see how symlinks or something like them can solve this problem.
> The link has to have something at the other end to link too after all.
> In the case of shared files/projects in VSS, the link is only internal
> to the VSS database (repository), externally each instance of the file
> can be different (they will get changes when the user does an update or
> 'get') or even not present if the user only has a working copy of one
> instance.
>
> Scott
>
> On Oct 6, 2004, at 1:45 PM, Monks, Peter wrote:
>
> > G'day Toby,
> >
> > Perhaps I should have been more careful to discuss use cases rather
> > than implementations. To my mind the notion of a "shared copy" is
> > what's important, and the unfortunate fact is that Subversion
> > currently only supports this notion on *nix platform (via symlinks).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 6 23:36:29 2004