Re: Upcoming FTPMaster meeting
On 2011-02-14, Luk Claes <luk@debian.org> wrote:
> On 02/14/2011 08:39 AM, Raphael Hertzog wrote:
>> On Sat, 12 Feb 2011, Guillem Jover wrote:
>>> On Fri, 2011-02-11 at 11:33:10 +0800, Paul Wise wrote:
>>>> On Fri, Feb 11, 2011 at 5:58 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
>>>>> Since there is no support for auto-building arch-independent binaries
>>>> I would hope that throwing away developer built debs would also apply
>>>> to arch-independent packages, IIRC that was part of the proposal.
>>>> There was talk of a Build-Architecture field for Architecture: all
>>>> stuff that can only be built on certain architectures (firmware,
>>>> bootloaders etc where there is no cross-compiler available).
>>> Using Build-Architecture would be a workaround, it should not be
>>> needed once multiarch is in place and those packages are built for
>>> their respective architectures.
>> While technically true, this can be discussed. I can imagine that you
>> might not want to configure multiarch on your system just because you
>> need some bootloaders files (e.g. syslinux-common in a CD build process).
>> Using multi-arch to solve this problem means changing the package from
>> arch: all to arch: i386 (or the specific arch set that you're interested
>> in).
> Build-Architecture would be used by the buildd network to see on which
> buildds the package can be built, so I don't get the "it's no problem
> once it's built" as that is a chicken-and-egg problem...
To be fair Guillem did address this. With multiarch you'd make it
arch:<specific arch> in that case and be able to install it on foreign archs.
(I.e. I could get my sparc BIOS through multiarch as it was built on sparc.)
You'd lose the notion of it being useful on other architectures (that's the
arch:all -> arch:i386 Raphael's talking about), though. But then packages
like qemu-system would just depend on openbios-sparc:sparc, no? If you
don't need to deal with them directly that'd be pretty transparent.
Also you could gracefully deal with something like debian-installer-netboot-
images, which would in theory need building on every
architecture, building a different arch:all on each of them. Multiarch would
result in the usual set of arch:any binaries.
But then so far multiarch didn't happen... ):
Kind regards
Philipp Kern
Reply to: