svn:externals in an added directory

[George Stein <ge...@go4more.de>]

<span style="font-family: Verdana"><font face="Courier New">Hi,<br /><br />We want to add a new directory with files to subversion. The newly added <br />files refers to sources from another URL. So we set svn:externals to <br />this directory. To ensure that our make works before committing the <br />changes we need to see the svn:externals. How can we achieve this?<br /><br />At the moment we have to commit the new directory/files first, then <br />updating it to resolve the externals, start the make and then commit <br />changes a second time. So we have two commits for one logical change. <br />This conflicts with our understanding of a changeset. And furthermore it <br />can leave the head of the repository in a not compilable state if the <br />make fails after the first commit.<br /><br />This also happens if we merge a branch with a new directory and <br />svn:externals back to the trunk. So working on a feature branch is no <br />solution to us. <br /><br />Any sugg!
 estions?<br /><br />Best<br />George<br /><br type="_moz" /></font></span>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn:externals in an added directory

[Ryan Schmidt <su...@ryandesign.com>]

On Jun 26, 2007, at 09:38, George Stein wrote:

> We want to add a new directory with files to subversion. The newly  
> added
> files refers to sources from another URL. So we set svn:externals to
> this directory. To ensure that our make works before committing the
> changes we need to see the svn:externals. How can we achieve this?
>
> At the moment we have to commit the new directory/files first, then
> updating it to resolve the externals, start the make and then commit
> changes a second time. So we have two commits for one logical change.
> This conflicts with our understanding of a changeset. And  
> furthermore it
> can leave the head of the repository in a not compilable state if the
> make fails after the first commit.
>
> This also happens if we merge a branch with a new directory and
> svn:externals back to the trunk. So working on a feature branch is no
> solution to us.

After setting svn:externals, or doing a merge which sets  
svn:externals, do an svn update. This will retrieve the external  
files. You don't need to commit first.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org