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

Re: Questions about svn:externals

From: Martin Rabl <martin.rabl_at_rablnet.de>
Date: Wed, 19 Jan 2011 10:26:58 +0100

Hi,

Am 19.01.2011 10:02, schrieb David Aldrich:
> 1) Subversion allows you to commit a change within the
> directory that uses the svn:external property.
> This change will not be committed to the referenced
> (source) directory/repo.
You mean: not to the repository, where the other repository is linked
into via svn:external?

> I can't imagine a circumstance where one would want
I work with several "mixed" repositories (they use the same libs,
referenced as externals), and it runs as I described.
Mostly - my experience - the externals are used for link (shared)
libraries or some other ressources used in several project or other
places in a trunk (last thing prevents doubles).

> to do this, so how can we prevent such commits being made?
IMHO there is no way to prevent external commits - it would be contrary
to the principles of svn, I think.

The only way is: "svn export" the contents, after that svn:ignore the dir.

> 2) What would happen if the developer did not have read access
> to the repo that is referenced in the svn:external?
> Would a checkout of the project that uses the external complete without error,
> except that the external code would not appear?
Hm, I think: the checkout will break. But I never checked this.
Give it a try ;-)

-- 
Greetings,
    Martin Rabl
Received on 2011-01-19 10:25:13 CET

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

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