On Sat, 2009-10-24 at 10:30 +0000, James Westby wrote:
>
> bzr-builder can be used to create "nested trees", but obviously can't
> represent them in bzr, so bzr-builddeb can't pick them up and use
> them.
> It's just one branch inside another. It could be extended to allow
> these things to be specified, but as nested trees were moving forwards
> waiting for that seemed like the better idea.
As an aside, config-manager is ~ bzr-builder, but without the debian
aspects or the merge command.
Anyhow, I don't think its a good idea to limit bzr-builder to the
least-functional subset of its capabilities - if no nest rules are used,
why not permit e.g. recording the result, pushing to a branch, doing an
incremental build etc.
On Sat, 2009-10-24 at 10:30 +0000, James Westby wrote:
>
> bzr-builder can be used to create "nested trees", but obviously can't
> represent them in bzr, so bzr-builddeb can't pick them up and use
> them.
> It's just one branch inside another. It could be extended to allow
> these things to be specified, but as nested trees were moving forwards
> waiting for that seemed like the better idea.
As an aside, config-manager is ~ bzr-builder, but without the debian
aspects or the merge command.
Anyhow, I don't think its a good idea to limit bzr-builder to the
least-functional subset of its capabilities - if no nest rules are used,
why not permit e.g. recording the result, pushing to a branch, doing an
incremental build etc.
-Rob