Re: Applications and Projects

On Wednesday, Sep 15, 2004, at 01:18 Australia, Ben Collins-Sussman
wrote:

> $ ls
> Proj1/ Proj2/ App1/ App2/

Yes Yes Yesssss!

I didn't think I was unclear at all, but yes, that is what I want on
export.

> If this is what you want, then heck, you don't need to change svn's
> source code. Just write your own 'export' script which looks for a
> custom 'depends' property which you invent and attach to directories.
> It parses the property value, and issues a bunch of 'svn export'
> commands. Extremely simple.
>
> This is exactly why properties are open-ended things. I can't see any
> reason to put this functionality into the core svn code; at least,
> I've
> never heard of anyone ever wanting to do something like this.

No, I never said that the core code should be changed. In my last mail
I talked about a script that issues separate "svn exports":

>> To confirm what I mean, when a Project is exported, the exporting
>> script would check if a 'depends' property is set on the project and
>> if
>> so it would issue separate "svn export" commands for each one listed.

If I had have intended this 'depends' property to be part of the core
functionality I would have called it the "svn:depends" property :)

I have been asking for confirmation that using a depends property,
along with a local 'svn' script in this way is OK to do. Thankyou,
you've answered that question. And I have also been trying to find out
if anyone thought this might cause any problem that I'd need to
consider?

Thanks again,

Brooke

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 15 14:43:41 2004