[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What happens when an architecture independent package won't build on all architectures?



On Thursday, March 01, 2012 11:26:01 PM Paul Wise wrote:

> 
> The Debian buildds do not (yet) build any Architecture: all packages,
> they are currently all built on developer machines.
> 
> IIRC there is a plan to build all packages on the buildds but that
> isn't yet in place.
> 
> Part of that is adding a Build-Architecture field for packages that
> are Architecture: all but can only build on certain architectures.
> 
> I guess the procedures for an Architecture: all package will be
> approximately the same as for Architecture: any packages where an
> architecture has multiple buildds. Give the package to one of the
> available buildds to try and if it fails, give it to another one.

When that plan goes into place, will the Architecture: all be built under all 
the different architectures? I have a package that fails to build under some 
archetectures, because of the heavy duty dependancies necessary to build an 
Architecture: all  package. I am trying to figure out if it would be a good 
idea to split that source package in two.

I am aware of Build-Depends-Indep and this kludge:
http://asylum.madhouse-project.org/blog/2012/01/26/buildd-workarounds/

but it feels too kludgy.

-- 
Paul Elliott                               1(512)837-1096
pelliott@BlackPatchPanel.com               PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/   Austin TX 78758-3117

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: