Sharing a vendor branch with 2 project repos?
From: David DL <ddl877_at_outlook.com>
Date: Fri, 30 May 2014 12:50:20 -0400
Hi All,
I'm trying to set up a by-the-book vendor branch, but I need to share it with two projects that exist in their own repositories.
The patches I need to maintain to the vendor code do need to be shared by both projects, so that makes things simpler I think.
Here is the structure I'm planning to use: (Hope the formatting makes sense)
# Repo 1: For vendor drops
./delivery_current
./delivery_tags/
./delivery_tags/delivery_1.0
./delivery_tags/delivery_1.1
./patched_current
# Repo 2: For ProjectOne code
ProjectOneRepo/trunk
svn:externals /VendorDropRepo/SomeVendor/LibA/patched_current_at_100 LibA
ProjectTwoRepo/trunk
svn:externals /VendorDropRepo/SomeVendor/LibA/patched_current_at_150 LibA
Question for the mailing list:
Does this seems like a good idea?
Thank you,
David
P.S. I think the vendor branch chapter in the svn book is missing an example command line for the second vendor drop tagging step. I've attached a patch that adds this. I'm guessing at the xml format, so take it with a grain of salt.
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.