On Fri, 1 Oct 2004 10:28:31 +0200, ark-d@betasystems.com
<ark-d@betasystems.com> wrote:
>
>
> Hi Patrick,
> hello SVN friends,
>
> you are pointing a very intresting issue: "Reuse" of (common) components
> among various projects / products.
>
> I think "externals" and "vendor branches" maybe two possible solutions for
> your scenario, which depends on whether you have to modify e.g. /lib5 in
> both projects independently or not. In the case you have to update and
> merge /proj1/lib5 and /proj2/lib5 from the originating updated /lib5,
> "vendor branches" could be the right solution for you. In other cases the
> "externlas" if you don't have to modify / branch the /lib5 in the working
> copies.
>
> --> did I understood your scenario correctly?
>
> You wrote:
>
> > but I would have trouble when it came to tagging and branching.
>
> --> which troubles?
>
> Best Regards,
> Arash
>
I'm responding to the list as it seems you intended to send the above
message to the list, although it came only to me. I'm interested in
teh case where the common component is updated for all users at the
same time - so having to merge from project to project provides no
value, just extra effort.
The issue with svn:externals as it is currently implemented is that if
you svn copy a directory that has svn:externals defined (to make a tag
or branch), the svn:externals still point to the same place, so when
you go to check out your tag or branch, the directories defined in the
svn:externals will be populated from HEAD. For this reason, you don't
easily get a real branch or tag when using svn:externals.
-Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 2 04:07:03 2004