On Sunday, Sep 12, 2004, at 13:22 Australia, Ben Collins-Sussman wrote:
> So I'm guessing here that you're looking for some sort of feature
> similar to CVS modules where you can say
> svn checkout module-thing
> And end up with a working copy that looks like
> If so, here's a way to get something similar: create a directory
> somewhere in the repository called "mymodule" (or whatever you wish).
> Make it an empty directory, or maybe just drop a README file into it.
> Attach an svn:externals property which checks out those three dirs as
> siblings. Then, when you run 'svn checkout mymodule', you get:
Yes, the behavior of CVS modules is what I'm after. What you suggest
sounds like it would work in many situations, but it doesn't really
solve my problem, I don't believe. If I have two projects then I'd
like both to refer to the same applications. The projects are
independent so they would have to have their own empty directories with
externals and thus their own App1 and App2. Right? It seems like I
would then end up with:
And for this reason I don't think your suggestion would work. Or am I
missing a hidden technique?
What do you think of the 'depends' property I suggested as a solution,
where a modified "svn export" would use the values to handle exporting
the dependencies also. The depends property would be set on each
project and list the Apps that it depends on. Then when the export is
done, the Apps are exported also. I may be able to use this for
checkouts also, but I'll have to do some experimentation to find out
what problems this may raise.
Am I out of my tree to attempt to build the 'depends' functionality?
Am I missing some way of using what Ben suggested?
You picked a fine time to leave me Lucile,
four hungry kids and a crop in the field.
-- Kenny Rogers
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 13 13:06:59 2004