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

Re: Checkouts of subsets of the tree

From: Mark Bohlman <mbohlman_at_tcicredit.com>
Date: 2004-06-25 18:32:57 CEST

Ben Collins-Sussman wrote:
> On Fri, 2004-06-25 at 11:05, Butler, Frances H (FHB) wrote:
>>I don't know about John, but this is a topic of great interest to my
>>development team. I would like more detail, please.
> I guess the real question is: is the 'svn:externals' explanation in
> chapter 7 unclear? Can you guys tell us how it's unclear? Ask specific
> questions?


    First congrats to you and all on the book, Subversion and your
musical - great work and thanks for all the efforts.

    I don't think the svn:externals is as clear as it could be, although
I've only played with it a bit. I ended up stumbling around trying to
get it set correctly (and I wish I had recorded it - but didn't - will
do so when I can get back to working on it in the next week or so...).

    What would be nice would be something like a concrete example of
being able to get from two repositories a working set of code. Say I'm
using Java, and want to get the source we develop out of
http://repos/trunk/src and the needed vendor jars out of
http://vendor/jars. In my working copy I'd want to be able to do a
"svn co http://repos/trunk/src" and then run ant or make to do a full
build, picking up the needed jars/libraries into the proper location.
Or a similar such scenario, for C/C++ or whatever.

    Having a concrete example to follow on doing something like this
would really help make it clear what was needed by the user, and I think
a lot of us using Subversion would benefit.

-- Mark

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 25 18:36:02 2004

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.