On 30.03.2012 13:41, Tobias Richter wrote:
> Hi *,
>
> I have some questions/suggestions for the Branch/Tag dialog.
>
> With the new TortoiseSVN version the dialog now shows all externals
> and has the possibility to set a explicit revision for these externals
> - that is great!
>
> 1. check externals per default to explicit revision:
> If I want to make sure that the new tag is always in a consistent
> state - and I want this always, I have to check all the externals to
> have their revisions fixed to their current working copy revision.
> Hopefully I or my colleagues never forget this. Is there a possibility
> to have them checked per default? Like setting an TortoiseSVN Advanced
> setting to true and then the dialog checks all externals always per
> default...
No, sorry.
Checking those by default is too risky. Since it's already too much work
for you to only check those, imagine they would be checked
automatically: you wouldn't even look at them first before branching!
But you *must* first look at them and verify the revisions it want's to
tag the externals to.
> 2. externals from tags - wrong revision:
> If I have some externals from a tag included, sometimes the found
> revision is "wrong" and the newly generated svn:externals property for
> the tag is not working. For example I have a Lib called Lib1 (rev 1).
> I create a tag from this Lib (Lib1/trunk) called /Lib1/tag/V02. - rev
> 2. Then I include this Lib in my App like svn:externals =
> "Lib1/Include ^/Libs/Lib1/tags/V02/Include". If I now try to create a
> tag for my App the Branch/Tag dialog looks for the externals and found
> the included externals. Now I can set them explicit to the found
> revision 1. BUT revision 1 is good for the Include directory but not
> for the tag (V02) directory because this folder was created in
> revision 2. Because of that behavior i cannot checkout the tag
> including the externals without errors like Lib1/tags/V02/Include not
> found in revision 1.
you don't have to (and should not) fix externals to a fixed revisions if
they point to a tag. A tag is by definition immutable.
> 3. create tag and set all externals to a given revision:
> If I create a new tag it would be nice if I have the possibility to
> set the same revision for ALL externals. Not just the last revision
> for each external which is found by TorotiseSVN - just let the user
> say: "Ok, I like to create a Tag and all my externals should be fixed
> at revision 200". This way the user can always checkout the tag
> including the externals without problems regarding the externals.
Also *not* a good idea.
* if only one external is not from the same repository, you get a broken
checkout
* if you forgot to update one of your externals before the branching,
then you're in trouble because you create the branch/tag for that
external to an unknown (unknown for you, and definitely untested) revision
If you however run an update first on the root of your working copy,
then the revisions of all externals (assuming they all point to the same
repository) will be the same anyway.
> I think that the solution: don't seta explicit revision for externals
> which are included from a tag is not really good because sometimes
> somebody delete Tags in the HEAD Revision and then the checkout won't
> working any longer...
"somebody delete Tags in the HEAD Revision" -> ????
As mentioned above, a tag is by definition immutable (to make this more
clear: a tag must never, ever be modified or even deleted). If you have
people deleting tags, then you really should be discussing your
practices with your team, and then come up with a solution that actually
works.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2942520
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-30 16:26:15 CEST