On Wed, Sep 26, 2007 at 06:38:02PM -0700, Steve Langasek wrote: > On Thu, Sep 27, 2007 at 11:11:40AM +1000, Paul Wise wrote: > > On 9/27/07, David Anderson <[EMAIL PROTECTED]> wrote: > > > > Possible solutions that we came up with on #debian-mentors: > > > The other possibility that was mentioned was to split the firmware out > > into a separate source package that produces an Arch: all package and > > then ensure that it is built on arm. > > > People in the channel had no idea if this would work though :) > > The only (good) way to ensure the arch: all package is built on arm is to > always do the sourceful upload of the package from arm. > > (Otherwise, you'd be building the arch: all package from the binary-arch > rule on arm only; this would work, but cause brain-twistiness wrt the > separation between arch: all and arch: any.) > I think that perhaps Paul meant to say an arch any package. If the code must always be compiled for a particular flavor of ARM processor, regardless of the host architecture of the machine which will be controlling the Lego, then it should be possible to build it is arch any, which would not get autobuilt anyways. Then, as long as the uploader (maintainer or NMU) buils on ARM, everything should be OK.
Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
