On Jul 22, 11:18 am, Robin Guest <robin.gu..._at_gmail.com> wrote:
> 2009/7/22 Robin Guest <robin.gu..._at_gmail.com>
>
> > Sure. I always manually add revisions to my externals before I tag them.
> > Takes all of 10 seconds extra. I change the svn:externals property in my
> > up-to-date wc, tag from the wc, leaving the wc pointing at trunk, then
> > revert it afterwards.
If you typically only have one or two externals then the '10 seconds
extra' and manual verification that you did it correctly may not be a
big deal. On the other hand, if you have a lot of externals that pull
together IP that is intended for reuse and that is still being
developed (possibly by multiple developers) you'll soon grow weary of
having to lock down each and every external (and wonder if you missed
one) prior to doing a build just so you can reliably reproduce the
source from the archive. The end result is either:
- No reliable place to go to get the latest/greatest IP for a
particular module (because each user of the module basically ended up
copying/replicating a snapshot and improved only their 'local'
version...maybe it got copied back to the trunk...maybe not).
- Or...you spend a lot of time and effort updating all of the external
links to lock them down...right when you're trying to finish up and
get a release out the door (bad timing for that task)
- Or...no reliable mechanism to exactly reproduce the source files
because the external link will always pull the head, not the revision
that was in place when the 'tag' was created.
>
> Another thing I regularly do is to make my externals point to tags of the
> external thing, rather than the trunk of the external thing. Since by
> convention tags are never changed, I'm then unlikely to get a wrong version.
> This doesn't guard against the target of the external being moved in the
> repo, though. Only an "@nnnnn"-style revision (peg revision) can cope with
> that.
>
And for relatively 'static' things that are externals, that's maybe
not so much of a hardship to do that extra work. If you consider
instead a project that is a collection of sub-projects where each of
the sub-projects is intended for reuse in other projects as well...and
everything (projects and subs) are all still under development you
might want to re-think that approach.
Again, I don't see this as a Tortoise limitation but a Subversion
one...but the Subversion folks don't seem to buy into this being a
limitation at all...in spite of the several requests and the existence
of svncopy.pl which explains the problem in detail as well.
KJ
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2374807
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-23 16:11:39 CEST