On Fri, Sep 22, 2017 at 3:08 AM Ralf Corsepius <rc040203@xxxxxxxxxx> wrote:
Hi,
I am trying to build a chain of packages in a build override?
I.e. a series of packages: A->B->C
I set up a build override for A, and B built successfully. Now, I would
have expect building C to pickup B from the A-override.
This does not seem to apply. C fails to build, apparently because
building doesn't pickup "B" from A's build override.
Is this a timing issue (Do I need to wait)? Do I have to setup another
build-override for B?
This is actually one of the places where the Modularity initiative really shines. With the module metadata, you specify all of the source packages that your module is going to need, along with an optional "buildorder" value that is basically a chainbuild indicator. All things with buildorder == 0 (or buildorder unspecified) will build roughly in parallel (as builders are available), then will generate a repo to supplement the buildroot for things with buildorder == 1 and so on.
So in essence, every module build is capable of being a chainbuild.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
