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

Re: Single file externals plan

From: Nathan Yospe <nyospe_at_gmail.com>
Date: Tue, 22 Apr 2008 16:37:43 -0700

On Tue, Apr 22, 2008 at 11:18 AM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> Blair Zajac <blair_at_orcaware.com> writes:
> > Here's my current thinking on behavior and implementation.

> > - Support only intra-repository file externals. This will allow the
> > svn client to effectively do a 'touch foo; svn add foo; svn switch URL
> > foo' to have a external in the wc (those actual commands only work in
> > a 1.5 client). So unlike a directory external, the .svn/entries file
> > has entries for file externals. This is needed for supporting all the
> > client commands on a file. I don't see modifying the existing
> > directory behavior.

> Before implementing this, it might be good to find out how often people
> use intra-repository externals at all. My guess (uneducated, anecdotal,
> etc) is: not much. Certainly most of the externals I set are coming
> from other repositories...

Single platform aliased views of a massive cross-platform repository.

This would make it much easier to have a checkout of (for example) a path
"branches/../root/cpp-aix/" that aliased only those portions of
"branches/../root/cpp/" that were relevant to building on aix.

I could use this to pull the cross-platform portions of the makefiles to the
right place in the tree.

Nathan F. Yospe

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-23 01:37:59 CEST

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.