Hi James, On Fri, Aug 28, 2015 at 10:09:43PM -0400, James McCoy wrote: > On Mon, Aug 24, 2015 at 12:49:58PM +0200, Johannes Schauer wrote: > > Quoting Michael Biebl (2015-08-24 09:56:02) > > > Am 24.08.2015 um 08:21 schrieb Johannes Schauer: > > > > Quoting Helmut Grohne (2015-08-24 07:32:16) > > > >> It is not clear how to implement :native for mk-build-deps, because it > > > >> does > > > >> not differentiate between build architecture and host architecture. > > > >> Maybe the > > > >> simplest fix would be to s/:native// in mk-build-deps and declare cross > > > >> support unfixably broken. Dima Kogan already observed that it does not > > > >> work > > > >> at all in #794538.
> > > > This is fixable. It has to be because building a binary package to
> > > > satisfy
> > > > dependencies already works in other situations while still being
> > > > cross-aware,
> > > > most notably in sbuild.
> > > > Namely, what mk-build-deps should do is to copy the sbuild behaviour:
> > > > - use libdpkg-perl to parse and process the Build-{Depends,Conflicts}*
> > > > fields
> > > > and filter architecture and profile restrictions correctly
> > > > - change the meaning of its --arch option (this currently does some
> > > > magic
> > > > depending on whether the source package has architecture specific
> > > > build
> > > > dependencies or not):
> No, --arch shouldn't be repurposed to mean "produce a deb that satisfies
> cross-build requirements". If you want to add new functionality, that's
> fine. Just don't break existing functionality while you're at it.
> Something like "mk-build-deps --cross --arch $hostarch" would be
> acceptable.
What existing functionality does this break? Using the --arch option to
mk-build-deps (with a foreign arch as argument), but not using the result
for purposes of cross-building, seems like an entirely theoretical use case
to me.
I'd actually been meaning for a while to talk to you about reopening bug
#565889 because that change completely broke cross-installability of
mk-build-deps --arch packages, which prior to that point worked for a great
number of packages. That's entirely superseded by this bug now, which I'm
perfectly happy to see even if it means I will have to use an additional
--cross argument.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
