"Erik Huelsmann" <ehuels_at_gmail.com> wrote on 01/07/2008 07:25:26 AM:
> On 1/7/08, Roth, Pierre <pierre.roth_at_covidien.com> wrote:
> >
> > > Note that I personally consider the VSS style shared sources
> > > a bad idea, because it is not at all visible which projects
> > > you are modifying with your "local" modifications. If a file
> > > is in a "common" folder or comes from a library that is more
> > > explicit and doesn't bear the danger of breaking.
> > >
> > I totally agree with you if subversion projects only include source
> > files. But as SVN is also used to store documents which may be shared
> > between projects without the "breaking risk", it could be interesting
to
> > have such a functionality. On platforms other than Windows, symlinks
> > could do the stuff but unfortunately I didn't choose mine... and
finally
> > got Windows :-(
>
> So what about the 'switch' functionality I proposed?
FYI, I believe file level svn:externals are being considered for 1.6.
The 'switch' concept is interesting if you can control all the clients
and automate the process with scripts. (I think <1.4 clients required
the source of the switch to exist in the original checkout, but I think
that isn't required now...) Pretty hard to modify graphical clients
like TortoiseSVN though.
It might be interesting to support some type of "automated" switching
in the client code, but that is bordering on ClearCase like config spec
functionality.
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-07 16:49:21 CET