I'm afraid we might not be able to build this bikeshed after all. ;P
* Paul Tagliamonte <paul...@debian.org>, 2014-02-26, 21:51:
For the implementation we might want to have a priority list. The
first architecture from the priority list that is allowed in
Build-Arch-Indep (or whatever) would build the arch:all packages. The
list would likely start with amd64 or i386 so that arch:all packages
without Build-Arch-Indep would be built on amd64 (i386).
Assuming that we (ab)use Build-Conflicts-Indep for restricting where
the package can be built, do we still need a per-package architecture
priorities? Wouldn't a global architecture priority list in wanna-build
be sufficient?
So, building off this mail (and ideas I had kicking around):
Build-Depends-Indep field is defined as a list of architectures that
the arch indep packages may be built on.
Architectures are parsed as splitting on whitespace (space, tab and
newline) as delimiter between the raw values. A package which defines
non-"any" values may not define "any" in the list of values. The
values are defined with the same values as the Architecture field,
with the exception of "all".
"any" may be interpreted as the prefered arch, which is advised (but
not required) to be amd64. If multiple values are provided, the first
value (only) will be used to build the arch:all package.
Any arguments on this rough concept?
What about architecture wildcards? Could I say
Build-Architecture-Indep: linux-any
?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140227115748.ga9...@jwilk.net
