Hi Steve,
your comment's very interesting. I think I will make a suggestion on the dev
list of subversion.
> But you have to keep in mind that this isn't an easy issue to fix:
> - just adding an '-rXXXX' to the property won't help if the externals
> project isn't from the same repository. The other repository might have
> a completely different revision
> - tagging such an external project isn't atomic anymore. So if someone
> else commits to the externals project between the time you tested your
> project and the time you finally tag your project, you won't have the
> correct revision added to the property.
hmmm, I quite don't understand the problem here. I think, there basically 2
cases, which are to handle:
1.) I make a tag: -> code freeze, all externals are freezed with their
current head revision. Okay, if the ext repos are heavily used by others, I
decide at beginning of developing to freeze the current state to the head
revision (or any other I know which is good), to be sure not having revision
glitches between testing and tagging. I think, the last one would be usual
in a team environment. I think, breaking up the atomic commit feature is
rather philosophical, because if you have several copies of external libs,
it's also not very handy.
2.) I make a branch and would like to include external improvements and
therefore all/some external version locks are removed.
In all cases, some kind of GUI frontend for easily managing this external
relations would be a nice benefit for TSVN e.g.. I think, implemented as
listview with Local Dir / Remote Dir / Revision would be really nice.
Revision could be a dropdown list with Head or user selected revision. How
about that ?
Bye,
Florian Storck
P.S.: My replies usually take enormous time until they show up in the list.
Is this normal ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Dec 6 09:16:50 2004