Hi,
Is it possible that you are packing your application incorrectly ?
From what I can gather, You have two projects Project A & Project B.
Now you have a file XXX in Project A that is also required by Project B.
If you "share" the files in Project B and change it then wouldn't you
also have to recompile, test and deploy Project A.
Why ? because your code in the repository for Project A no longer
reflects Production !
Should you not consider a component based development. Where you will
have Project A & Project B and Component XXX. This way you have the file
in one location. Project A will depend on ComponentXXX-1.0 and Project B
will depend on ComponentXXX-2.0.
And everyone is happy :)
Thanks
Lakshman
> -----Original Message-----
> From: Robert Denton [mailto:robert@headsprout.com]
> Sent: Thursday, 7 September 2006 6:24 AM
> To: users@subversion.tigris.org
> Subject: Re: Best way to handle shared files in SVN?
>
> On Sep 6, 2006, at 2:16 PM, Andy Levy wrote:
>
> > 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
> >
>
> Hm.
>
> I have googled on the matter to some degree and the general
> concensus, as far as I can tell, is that this is a highly sought
> after feature, and most of the posting I saw argued that using
> svn:externals is NOT a solution, nor a work-around, since you can
> only apply that property to folders and not files.
>
> So given that svn:externals does not equate to VSS sharing, what
> other solutions have people come up with to achieve this?
>
> I hope me and my boss are not the only two people on the planet who
> valued this feature in VSS. Are there any plans for building it into
> SVN?
>
> ---------------------------------------------------------------------
> 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 Thu Sep 7 03:28:12 2006