Re: AArch64 planning BoF at DebConf
On Jul 21, 2012, at 04:10, Luke Kenneth Casson Leighton wrote:
> On Fri, Jul 20, 2012 at 4:12 PM, Steve McIntyre <firstname.lastname@example.org> wrote:
>> I'm hoping to get AArch64 bootstrapped and ready for release in Debian
>> by Wheezy+1, which I acknowledge will take a lot of work in a
>> comparatively short space of time. We will need to cross-bootstrap as
>> much as possible, verifying things in the model. Existing bootstrap
>> work done by Wookey and co. will help a lot here.
> @begin awkward embarrassing moment, feel free to gloss over....
> i also made some recommendations and offered to knock together a build
> infrastructure which would have augmented the existing debian build
> system, (which would have leveraged the best free software
> cross-compiling and qemu-compile-enabled toolchain that there is, and
> made it debian-aware)
I'm assuming you're talking about Yocto/OE/bitbake/poky -- can you confirm?
> but the recommendations were, sadly, viewed as -
> once again - "oo the fuck's this lkcl telling us what the fuck to do,
> we've been doing this for years, oo der fuck does ee fink ee is,
> trying to take over debian, let's vilify him, deliberately
> misunderstand what he's saying as much as we can as often as we can,
> make him look a fool so we look good and he'll go away ahhh that's
> better: we can go back to doing it our way, now, and stay in control
> yessss" rather than being viewed as what they were offered as: an
> augmentation of and an enhancement of the existing debian build
> system, offered *without* prejudice and entirely in good faith.
Pejorative poetry aside, I think there are some reasonable choices made by Debian with regards to the build system, particularly building directly on the hardware. Is there a case to be made that using qemu and cross-compiling is somehow better? What are the trade offs?