Update to revision and externals

[Norbert Unterberg <nu...@gmail.com>]

Hi,

Is there a way to let svn:externals use the same revision number as
the folder they are contained in?

To clarify:

We have a project that contains a few svn:externals which point into
the same repository (using ../ or ^/ syntax).
Problem is that when we need to go back in time with the project for
some reason and do an TSVN --> Update to revision ... then the
externals are still updated to their HEAD revision and not to the
revision that was given in the update command. Is there any option,
flag or external property syntax to let the update revision propagate
to the externals, so that both the working copy and the externals are
on the same revision number?

Regards
Norbert Unterberg

Re: Update to revision and externals

[Norbert Unterberg <nu...@gmail.com>]

2010/12/14 Ryan Schmidt <su...@ryandesign.com>:
> On Dec 13, 2010, at 04:27, Norbert Unterberg wrote:
>
>> We have a project that contains a few svn:externals which point into
>> the same repository (using ../ or ^/ syntax).
>> Problem is that when we need to go back in time with the project for
>> some reason and do an TSVN --> Update to revision ... then the
>> externals are still updated to their HEAD revision and not to the
>> revision that was given in the update command.
>
> ....only if you've defined your externals without a revision argument. You should always define your externals with a revision argument, a peg revision in fact, so that when you update to previous versions of your project, your externals go back as well. This also gives you concrete times at which you update your externals to new versions of that external software, instead of having them auto-update, as it were, and possibly break your project in the process.

I will think about that. The problem is that in our case the external
is not really "external" but points to a different folder in the same
active project (please no discussion here why that is so). So normally
we want to work with "trunk" of both projects without daily
modification to the externals property. I just thought there might be
a switch to make "svn up -rxxxx" a real time machine.

Norbert

Re: Update to revision and externals

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

On Dec 13, 2010, at 04:27, Norbert Unterberg wrote:

> Is there a way to let svn:externals use the same revision number as
> the folder they are contained in?

Not that I'm aware of, unless you write a script to do so.

> We have a project that contains a few svn:externals which point into
> the same repository (using ../ or ^/ syntax).
> Problem is that when we need to go back in time with the project for
> some reason and do an TSVN --> Update to revision ... then the
> externals are still updated to their HEAD revision and not to the
> revision that was given in the update command.

....only if you've defined your externals without a revision argument. You should always define your externals with a revision argument, a peg revision in fact, so that when you update to previous versions of your project, your externals go back as well. This also gives you concrete times at which you update your externals to new versions of that external software, instead of having them auto-update, as it were, and possibly break your project in the process.