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

Re: bug report: checkout and export ignore given command line revision number for svn:externals that haven't self a -r

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-03-12 20:59:45 CET

On 3/11/07, Bernd Derer <Bernd.Derer@web.de> wrote:
> The checkout and the export command with given revision number at
> command line, check out the HEAD version of externals that
> haven't self a revision number. That is wrongly, correctly would be
> the requested version.

Actually, no. The behaviour you're seeing is the way externals have
been designed (ie, it's not a bug): they have been designed to point
to other repositories. In secondary repositories, the revision number
from the primary repository has no meaning.

For example, if you had primary repository A at revision 12000 and
secondary repository at revision 500 (a young project), you'd have a
lot of problems when backdating the main repository tree to r11999,
because that revision doesn't in repository B.

What you're experiencing is the fallout from using externals for what
they haven't been designed for.

What you *could* do however is use the switch command to emulate
intra-repository links: Create empty directories where you have your
module dependencies and 'svn switch' those directories to the parts of
the tree where your deps live. (You could use a wrapper to do that for
you.)

If you then backdate (update with a historical revision) the tree,
you'll also see the modules be updated.

HTH,

Erik.

 The bug is in all (Windows?) SVN versions,
> inclusive Subversion 1.4.2-r22196.

> More detailed:
> We use extensively svn:externals properties that haven't set a
> revision number. We need this, because all our changes in a common
> library should immediately effect all HEAD versions of projects that
> use this library. In addition saves us that a lot of work, which we
> would have otherwise with the administration of the version numbers
> for each external link.
> All right, so far. But the bug disabled that we can check out a non
> HEAD version of any project with one checkout command. We must
> manually update every external link to the correct version. This is a
> very frustrating job. I thing, nobody need Subversion current checkout
> behavior regarding externals without a revision number, therefore it's
> a bug in my point of view. If you don't agree with me, I would be
> happy, if someone implement a checkout/export option that enforcing the
> expected behavior.
>
> Thanks in advance!
> Bernd Derer
> (Sorry about my poor English)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 12 21:07:08 2007

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