[Multiarch-devel] multiarch cross build dependency resolution

[Wookey]

+++ Johannes Schauer [2016-01-04 13:39 +0100]:

> With that in mind: what is the advantage of using "apt-get build-dep" over
> "apt-get install"? The latter method is tried and tested with native builds.
> The former method is less tested as it's only used for cross builds. Why switch
> to the build-dep method?

My understanding for cross-building is that 'apt-get build-dep' is the
definitive method to get the right build-dependencies for a package
with all the multiarch dependencies properly resolved. That's why I
used it originally - nothing more complicated than that.

This is the way that all the multiarch crossbuilding has been done for
a few years now so it's quite well tested in its context too. I agree
that there is a difference between native and cross builds here which
it would be good to eliminate for consistency. Which leads to the
question: Why not go the other way and use apt-get build-dep for
native builds too? Why do we use the dpkg parsing to make a dumy
package instead? (I'll read the rest of the therad now which may
answer this question). There have been differences between apt and
dpkg multiarch dependency resolution in the past but we are working on
eliminating those and everyone involved agrees that such differences
are bugs.

I'll have to read the referenced bugs and have a think about whether
there are reasons why your suggested alternative would be
better/worse.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/multiarch-devel/attachments/20160106/32a08aed/attachment.sig>