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

Re: Problem with the present handling of svn:externals

From: Steve Greenland <steveg_at_lsli.com>
Date: 2005-02-23 00:35:59 CET

On Tue, Feb 22, 2005 at 12:15:33PM -0500, Dale Worley wrote:
> > From: Steve Greenland [mailto:steveg@lsli.com]
> >
> > Uh, no. Several people have noticed that tagging and branching "don't
> > work" with externals for precisely this reason. The problem
> > is that the
> > definition of "works" varies with circumstances, and finding a general
> > solution is hard.
> If you are doing tagging/branching, you really should be using svncopy.pl,
> which allows you to specify the further information you need to get the
> results you want.

Oh, that's *so* close. It solves tagging acceptably, and almost does
what I want for branching.

See, I'm stupid. If I have to remember to branch each of the external
projects with the one I'm working on, I'll forget. Or if I write a
script, I'll be on the wrong machine. Etc. All solvable problems, but
annoying. And I *really* don't want to branch the whole tree, it just
doesn't make any sense for our setup. But with a little hacking, I ought
to be able to make it read the svn:external and add it to the branch
list itself, and then reset the value of svn:external to the new point.

Too bad it didn't make the 1.1 branch. I think I'll bug the Debian folks
to add it anyway...

Thanks for the pointer,

"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 23 00:39:23 2005

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.