Re: Local {amd,sparc}64 builds revert to *.tgz sets?

[David Brownlee <abs%absd.org@localhost>]

On Wed, 21 Nov 2018 at 15:28, Martin Husemann <martin%duskware.de@localhost> wrote:
>
> On Wed, Nov 21, 2018 at 03:24:28PM +0000, David Brownlee wrote:
> > Maybe abort the build with an error - its asking for an unresolvable
> > combination. Anything else violates the POLS.
>
> I disagree - it just works (independend of which option wins). Who cares
> what compression format is used in the end besides maybe some local scripts
> that can easily be adjusted to deal with both?

Then at the very least we definitely need to update the docs. bsd.README states:

USE_XZ_SETS     If "no", use the host "gzip" program to compress sets.
                Otherwise use xz to compress things.
                Default: "yes" for architectures with "enough" memory to
                decompress, "no" for older ones.

Why would I as a user expect USE_PIGZGZIP to break USE_XZ_SETS, or conversely
USE_XZ_SETS to silently ignore USE_PIGZGZIP. That reeks of hidden magic.

David