Thanks for your answer.
Here is what I want to do:
My repository tree structure is:
| |- component1/
| |- component2/
| `- component3/
`- platform1/ <- svn:externals
"platform1" refers to "component1",2,3 thus what I need after a checkout of
So the only way (that I've found) to automate this (excluding the individual
checkout of the 3 components and the platform) would be to add svn:externals
properties on the "platform1/" directory as follow:
But ../component1/ is not supported...
If I put the svn:externals on the parent directory (here it's "platforms/").
I can obtain the following tree structure after a checkout of "platforms/":
But it's not what I want to do. I really need to force the checkout of the
three components during the checkout of platform1 and not platforms.
You may think that it's the design of my repository's tree structure which
is not adapted, but I have other constraints which force me to build it like
De : Blair Zajac [mailto:blair_at_orcaware.com]
Envoyé : jeudi 5 février 2009 20:43
À : Dimitri Yanculovici
Cc : dev_at_subversion.tigris.org
Objet : Re: svn:externals ../ in local path
Dimitri Yanculovici wrote:
> I would like to know if the ../ in the local path of an svn:externals
> definition is planed to be supported.
> It isnt in the 1.5 version of svn : Also, the local subdirectory part
> of the definition cannot contain .. parent directory indicators (such as
> Is there a bug (enhancement) already opened for that in the subversion
> issue tracker?
> I didn't find one.
No, it was a deliberate design decision not to support that. If you want an
external to be dropped into a directory above the directory with the
svn:external property, you need to move the property up to a level that has
external checkout location to be a subdirectory.
What are you trying to do?
Received on 2009-02-06 11:27:43 CET