Closed MingcongBai closed 8 years ago
Added a blacklist scheme.
# foo/defines
arch_exclude 'arm*'
Can this still be factor'd into a variable? That would really make life easier...
Ugh, why a variable…
Ugh, why a variable…
Imagine out of nowhere comes a scheme-like command...
Hmm…… I can move this to defines
actually.
With a single extglob… Right.
But still I have to say I prefer blacklisting so…
Well simply assume whenever a file is sourced with extglob...
But still I have to say I prefer blacklisting so…
Fine by me.
With the negate
glob operator, you can do something like !(amd64|armel)
.
Why would I want that...?
Because not(not(amd64 or armel)) is amd64 or armel, and that's what available means.
(God... I am always mixing this up with "given that") Don't mind me.
Proposing support for listing on what arch the package will build, and those not on the list will not. For example:
Then, when running with
ARCH=amd64
, the build goes on as usual. If running onARCH=armel
, then...When
AVAILABLE_ARCH
is left blank, then all architectures are free to build this package.