Hi, On Thu, 24 Dec 2015 11:11:58 +0100 Johannes Schauer <jo...@debian.org> wrote: > Maybe a good fix would already be to properly document how --source, > --arch-all and --arch-all-only play together. Here is an overview of which > combination of these options leads to which flag being passed to > dpkg-buildpackage: > > --source | --arch-all | --arch-all-only | dpkg-buildpackage flag > ------------+--------------+------------------+------------------------ > set | set | set | -g > set | set | | > set | | set | -S > set | | | -G > | set | set | -A > | set | | -b > | | set | > | | | -B
actually above table is partly a lie. The --arch-all-only option, while being the only option that can set the BUILD_ARCH_ANY configuration variable is *also* setting the BUILD_ARCH_ALL variable so it has to be used together with --no-arch-all directly after it in cases where --arch-all is not set. This will be vastly simplified with the --arch-any and --no-arch-any option from bug #799056. Thanks! cheers, josch
signature.asc
Description: signature
