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

Re: svn:externals in an added directory

From: George Stein <george.stein_at_go4more.de>
Date: 2007-06-26 17:56:12 CEST
On Jun 26, 2007, at 17:07, Ryan Schmidt wrote: 

> 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.

This seems only to be true if you set svn:externals to a previously
added and committed directory.

For the following use case

$ md new_directory
$ svn add new_directory
$ svn ps svn:externals "ext_dir ext_URL" new_directory
$ svn up new_directory

the svn up doesn't update my new_directory. Could you/anyone verify
it, please?


--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on Tue Jun 26 17:56:03 2007

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.