Hello,
I have a question/problem that I am hoping someone can help me with. We
have been using Subversion successfully for a few years, but have
recently run into a little problem with our extensions.
We have a repositiory for libraries (that can be distributed alone or
used with an application). Over time, some of the libraries that were
added used other libraries in the respository. For example:
libs/libA
libs/libB -> external depend libA
libs/libC -> external depend libB
libs/libD -> external depend libA
libs/libE -> external depend libC
In isolation, if we were to distribute (via checkout) libs C and D
separately to two separate clients, they work peachy. However you can
see if if we had an application in another repo that depended on libs C
and D (and the external property checked out into a "deps" subdirectory)
the hierarchy would look like this:
app/deps/libC
app/deps/libC/deps/libB
app/deps/libC/deps/libB/deps/libA
app/deps/libD
app/deps/libD/deps/libA
The build tree, as Scons checks it out, contains two separate copies of
the libA source code. This is because, as far as I can tell, the
svn:externals propery only assumes that it is the at the root of a
checkout and goes into a subdirectly only. It really hates absolute
paths and the ".." path.
It seems to me then that the externals property doesn't scale well. It
would be nice if there was a way to tell an external that it was in fact
not the root of its own tree and that a specifier of some kind would add
more flexibilty in where the external checkouts could go.
Am I missing something, or is there some kind of strategy I can use
other than having all of my code in one big tree and checking it all out
whether I need it or not?
Thanks,
George Ryan
Senior Software Architect
Akoostix Inc., Nova Scotia Canada
902-404-PING | www.akoostix.com
The information contained in this e-mail may contain confidential
information intended for a specific individual and purpose. The
information is private and is legally protected by law. If you are not
the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the
comments of this information is strictly prohibited. If you have
received this communication in error, please notify the sender
immediately by telephone or return e-mail.
George Ryan
Senior Software Architect
Akoostix Inc., Nova Scotia Canada
902-404-PING | www.akoostix.com
"Simplicity and elegance are unpopular because they require hard work
and discipline to achieve and education to be appreciated."
- Edsger W. Dijkstra
The information contained in this e-mail may contain confidential
information intended for a specific individual and purpose. The
information is private and is legally protected by law. If you are not
the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the
comments of this information is strictly prohibited. If you have
received this communication in error, please notify the sender
immediately by telephone or return e-mail.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=987945
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-20 01:51:55 CET