Re: the state of thought on inter-/intra- project linking/sharing/externals

On 29.12.2005 15:03, Molle Bestefich wrote:

>>2) commits aren't recursive. (how about updates? etc?) I can immagine
>>situations where you may want recursive or non-recursive commits. should
>>this be added, perhaps, as a per-external setting?

Right - commits are non-recursive, which is often very painful. And
while updates are recursive, the options such as "-r nnn" are not
inherited - which makes perfect sense for the
intra-repository/intra-project links, but is very inconvenient for
inter-project externals.

> Agreed, commits should be atomic if the svn:external points to
> something inside the repository itself.
>
> Would need to make the code know whether the svn:externals is really internal.
> Either by adding support for relative paths, eg. starting with /
> instead of <protocol>://, or by creating a new property
> "svn:internals".
>
> I imagine that "svn:internals" is the nicer solution.
> There might be less shortcuts in the code, it'll probably be a few
> lines extra in fact, but explaining and documenting things should be
> much more straightforward.

I agree that "svn:internals" s probably the best way to go - this way it
is become very natural to distinguish between an "internal" link and an
"extarnal" link to a different project that just happened to reside on
the same server.

P.S. See also
http://subversion.tigris.org/issues/buglist.cgi?issue_id=937,1167,1258,1336

937 svn:externals should work with files as well as directories
1167 svn:externals handling on commit (companion to #959)
1258 tag svn:externals on copy
1336 svn:externals should allow relative paths

-- 
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org