Release config file syntax

[Alexander Belchenko]

Gordon Tyler пишет:
> On Tue, October 12, 2010 12:18 pm, Vincent Ladeuil wrote:
>> On the other hand, since the OSX installers already use sub-directories
>> (and I suspect the windows installers do the same), we may want to use
>> scmproj or bzr-externals...and we may as well package them no ?
> 
> I have no idea how scmproj or bzr-externals work. I'm reluctant to
> shoehorn this into something that wasn't designed to manage this. 

To manage what?

The whole idea behind scmproj and bzr-externals is to automatize
checkout of complex project with all its dependencies. bzr-externals
works seamless because it's using hooks. scmproj required user to use
new commands. But the core idea is mostly the same.

For both you can configure every component of your complex project:
* where from to get it on checkout/branch/pull
* where to put it in the working tree
* explicit revision (revno, revid, tag, etc)

Then everything else will be done for you by plugin.

So, without looking at your code I can't say how close you to
re-implementing those plugins, but at least the main idea you are.

Anyway, that's your call, even if for me it sounds like NIH. My past
attempts to introduce scmproj to handle build configuration have
failed. That's a karma, I guess.

> And I'm
> not sure what you mean by packaging?

By packaging Vincent means "put these plugins into installer", right
Vincent?

I think it might have sense to add bzr-externals into set of bundled
plugins, unless bzr 2.3 will ship Nested Tree feature.