[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: Talden <talden_at_gmail.com>
Date: 2007-06-27 01:41:08 CEST

This is another case of existing working copy content not being used in
preference to server data.

There are a few instances of this floating around already (EG pulling a copy
of a path that you already have checked out). I expect that solving them is
non-trivial so I wouldn't expect this to change any-time soon.

Besides, I'd much rather efforts were spent on a more radical alteration to
the working copy model than filling in these few performance gaps.

--
Talden
On 6/27/07, Ryan Schmidt <subversion-2007b@ryandesign.com> wrote:
>
> On Jun 26, 2007, at 10:56, George Stein wrote:
>
> > 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?
>
> Ok, that seems to be true. I don't know if that's the intended behavior.
>
> As a workaround, you could "svn co" or "svn export" the external URL
> to the correct place within the working copy for testing purposes,
> until you commit.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Wed Jun 27 01:40:56 2007

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