[buildd-tools-devel] Bug#809730: Bug#809730: sbuild: use build profiles when resolving cross build dependencies

[Johannes Schauer]

Hi,

Quoting Niko Tyni (2016-01-03 15:54:20)
> On Sun, Jan 03, 2016 at 03:38:54PM +0100, Johannes Schauer wrote:
> > Also back when I implemented build profile support in sbuild it was working
> > just fine. Looking at the code now it still should.
> 
> Just in case it wasn't obvious: the code path here is specific to the cross
> build dependency resolving.
> 
> > Also, because we must support apt in old-old-stable we cannot just push the -P
> > argument to the apt-get invocation since this will break apt pre-Jessie.
> 
> Ah, that's unfortunate. Does cross building really work on oldoldstable?

does it really work on stable? ;)

The thing is that using the sbuild dummy package means that apt does not have
to be able to resolve crossbuild dependencies nor does it need to be aware of
build profiles. Sbuild (or Dpkg::Deps::deps_parse in particular) take care of
that and create a dummy package with the right dependencies.

> Maybe 'apt-get -o "APT::Build-Profiles=[...]" would work instead?  It looks
> like apt-get ignores unknown configuration variables.

Correct, old apt ignores configuration options it doesn't know about. But
again, apt doesn't need to know about the enabled profiles because sbuild
already took care of that for it.

Thanks!

cheers, josch
-------------- 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/buildd-tools-devel/attachments/20160103/5bf60f27/attachment-0001.sig>