[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Separate binary and binary-independent builds



Hi Daniel,

Le mardi, 23 février 2016, 11.00:57 Daniel Reurich a écrit :
> We're trying to build Cups for Devuan using Jenkins CI, and have run
> into an issue with circular dependencies between the arch-independent
> and arch dependent packages during the build.

If you want to bootstrap cups, please see: 
https://bugs.debian.org/734670 . In short, you need to build with 
'nocheck' in DEB_BUILD_OPTIONS and without cups-filters and friends in 
Build-Depends, initially. Then build cups-filters, then rebuild cups. 

It's arguably not perfect yet, and would benefit from Build Profiles 
support: https://wiki.debian.org/BuildProfileSpec

Wookey: can this be implemented in cups' debian/control already ? If so, 
how?

> Additionally we seem to get the binary targets built when building the
> binary independent package and the binary tests are run - which
> depends on the binary packages.

'nocheck' is the way to answer that.

> Of course we can't build the binary packages because they need the all
> target to run the test suites.
>
> To me it looks like it's a structural issue with upstream which isn't
> easily fixed.

No. It's a bootstrapping issue, which you need to address at your end.

> So can I suggest
> a) skip the running the auto-test suite for the arch-independent build

'nocheck', really.

> b) look at teasing out upstreams build targets in debian/rules to
> separate them into binary-dependent and binary-independent targets to
> reduce wasted time rebuilding the documentation for every
> arch-dependent build and building the binary stuff in the
> arch-independent build.

Roughly said, I don't care about buildds "wasting time", as long as the 
resulting packages are fine.

> I'd appreciate your thoughts and would be keen to collaborate to get
> this done.

I welcome patches :) As mentionned above, build time is not an problem 
worth breaking packages, or disabling test-suites permanently: disabling 
them temporarily is perfectly fine at your end, if you're bootstrapping 
cups, as long as you rebuild it with tests before shipping to your 
users.

-- 
Cheers,
    OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: