Re: Checkouts of subsets of the tree
From: John Rousseau <JRousseau_at_novell.com>
Date: 2004-06-25 18:42:02 CEST
On Fri, 25 Jun 2004 11:18:53 -0500, Ben Collins-Sussman <sussman@collab.net> wrote:
> On Fri, 2004-06-25 at 11:05, Butler, Frances H (FHB) wrote:
I don't have a CVS background, and I've been using ClearCase long enough that the twisted way it does some things seems like the best approach. I'm also (obviously) a subversion noob.
My thought is to create a "jdk" repo with trees for all the platforms that I need. I would then need to create a directory in the main repo that had externals properties pointing to the JDK repo. What I don't know how to do is, on a per-client basis, allow them to choose the value of the externals target.
As I'm writing this, I'm thinking that putting the different platform code into two branches in the jdk repo might be better, but I still come to the same problem. How do I have the externals link point to different places in the jdk repo for different users? I don't really need the externals property to point to different things, but if they point to the same place then I'm still stuck as to how to only load (checkout) part of it.
I could see this working if each user checked out the "jdk" directory in the main repo and made the externals ref correcct for them, but that seems a little hacky.
I'm sure it's a mindset problem on my end and not a documentation one, but I can't see through to the solution.
Thanks
-- ---------------------------------------------------------------- John Rousseau JRousseau@novell.com Novell, Inc. Phone: +1 781 464 8377 404 Wyman Street Fax: +1 781 464 8100 Waltham, MA 02451 http://www.novell.com ---------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.orgReceived on Fri Jun 25 18:46:53 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.