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

Was: [PROPOSAL] Incomplete working copies (issue #695)

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2006-07-14 11:50:15 CEST

Erik Huelsmann wrote:
> svn:externals has this property: it downloads source code from another
> repository and prevents commits when committing the container.

Luckily it only prevents commits if the svn:external is in another repository.
Otherwise we'd be in big trouble :-)...

(Perhaps this is a property of TSVN not SVN, not sure.)

> This can be achieved as follows:
> Say you have projects /foo-1 and /foo-2 where /foo-2 also is a
> subcomponent of /foo-1. Now you can create an (empty!) subdirectory in
> the /foo-1 module - say /foo/bar - and then switch the directory to
> the /foo-2 tree. Now, commits to /foo/bar will be sent to /foo-2 and
> commits to /foo-2 will be pulled into /foo/bar.

The problem with this approach is that you're turning the whole thing
into a manual process which has to be done for every developer on the
team, for every checkout of a project (s)he makes, every single time.

Kind of the same reason why TSVN's Global Ignore feature is so popular
- svn:ignore doesn't work in many real world scenarios because
Subversion lacks inherited properties.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 14 11:50:43 2006

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

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