[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Bundling folders with svn copy and vendor branches

From: Robert Hunter <robert.hunter_at_gen-i.co.nz>
Date: 2004-11-09 02:01:46 CET

I am trying to use vendor branches to manage some third-party add-ins for a
project,
but I'm having difficulty finding a clean way of collating the vendor
branches.
(I'm also having difficulty tying down my explanation without resorting
to show-and-tell, but please bear with me.)

If I have a structure like the folowing:

/vendor/libcomplex/current/
/vendor/libcomplex/1.0/
/vendor/libcomplex/1.1/
/vendor/libgeometry/current/
/calc/trunk/add-ins/
/calc/trunk/add-ins/polygons/
/calc/trunk/add-ins/solids/
/calc/trunk/add-ins/arithmetic/
/calc/trunk/add-ins/storage/

How can I maintain the add-ins folder when there is a new
release of "libcomplex"?

Each of the product vendor releases have several sub-folders,
but the project itself ("calc" in the above example) requires
that all of these sub-folders appear flat in the "libraries"
folder.

So the vendor branches look like this:

/vendor/libcomplex/current/arithmetic/
/vendor/libcomplex/current/arithmetic/addition.c
/vendor/libcomplex/current/storage/
/vendor/libcomplex/current/storage/database.c
/vendor/libcomplex/current/VERSION.txt

/vendor/libgeometry/current/polygons/
/vendor/libgeometry/current/polygons/triangle.c
/vendor/libgeometry/current/solids/
/vendor/libgeometry/current/solids/cube.c
/vendor/libgeometry/current/VERSION.txt

My initial reaction was to try something like the following:
        svn copy /vendor/libcomplex/current/* /calc/trunk/add-ins/
However, "svn copy" takes only one source and one destination
argument.

        svn delete /calc/trunk/add-ins/arithmetic/
        svn copy \
                /vendor/libcomplex/current/arithmetic \
                /calc/trunk/add-ins/arithmetic

But doing this (working-copy to working copy) results in the error
message "svn: Entry already exists".

I really would prefer the whole operation involve only a single
commit -- I would hate to have a "mixed bag" of versions sitting
around in the same folder accidentally!

Can someone please point me in the right direction, or help me with
search terms that might turn up relevant results?

Even just a definitive answer telling me that I'm "missing the point"
and "shouldn't be doing that" would be useful ;-)

Thanks,

-- 
Robert Hunter
*****************************************************************************
This communication, including any attachments, is confidential.
If you are not the intended recipient, you should not read it
- please contact me immediately, destroy it, and do not copy
or use any part of this communication or disclose anything about it,
Thank you.
Please note that this communication does not designate an information system
for the purposes of the Electronic Transactions Act 2002
******************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 9 02:02:36 2004

This is an archived mail posted to the Subversion Users mailing list.