Questions about build system

[Dan Williams]

On Wed, 2006-03-01 at 19:28 -0800, Denis Leroy wrote:
> I'm maintaining a number of packages that are part of a long dependency 
> chain  (gcdmaster -> libgnomeuimm -> gtkmm -> glibmm -> libsigc++). Does 
> that mean that, in order to guarantee that each one of these is build 
> against the newly rebuilt versions, I have to queue them up in the build 
> system, say, libsigc++ on monday, glibmm on tuesday, ..., and gcdmaster 
> on friday :-) ?
> 
> I know that mock doesn't handle this like mach does: freshly built 
> packages in /var/lib/x/result are not automatically used in the prep 
> phase of the next mock build, and that's currently my biggest gripe 
> against mock (with otherwise works great). So since plague uses mock, 
> does this also apply to our build system ?

There's this great new depsolving buildsystem update that we've all been
hearing about recently...  Which should fix your problem.  You queue up
a job, and the job doesn't start to build until all of its dependencies
are solved.

Yes, this means that if you don't have a hard Requires: foo >= 1.2 and
you are waiting to build bar because it depends on the latest foo, you
must make that explicit.  But that's life.

Should hopefully come along this month.

Dan