[Multiarch-devel] multiarch cross build dependency resolution

[Johannes Schauer]

Hi,

in #809730 Niko Tyni made me aware that sbuild is using 'apt-get build-dep' to
resolve cross build dependencies. This feature seems to originate in a commit
by Wookey [1] and later by Colin Watson [2]. I'd like to get rid of it and my
question is why 'apt-get build-dep' was used in the first place?

As far as my understanding of multiarch goes, letting sbuild generate a dummy
binary package of the host architecture depending on the build dependencies
which were properly mangled by Dpkg::Deps::deps_parse() and telling apt to
install that binary package should be sufficient, no?

Unfortunately, commit messages and code comments do not tell me why 'apt-get
build-dep' was used if hostarch != buildarch.

What am I missing?

What prevents a dummy package being used instead as it is done in the native
case?

Thanks!

cheers, josch

[1] https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=6083686e052ddf5a03b9e2475bd99152a9f6e697
[2] https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=9aaa06de161ecb0a5422dc48805215211590c2f9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/multiarch-devel/attachments/20160103/864d36fd/attachment.sig>