[OE-core] [PATCH 2/2] uninative: Switch from bz2 to xz

[richard.purdie at linuxfoundation.org]

On Thu, 2019-05-30 at 11:57 -0400, Tom Rini wrote:
> On Thu, May 30, 2019 at 02:55:35PM +0100, 
> richard.purdie at linuxfoundation.org wrote:
> > On Thu, 2019-05-30 at 06:32 -0700, akuster808 wrote:
> > > On 5/30/19 1:13 AM, richard.purdie at linuxfoundation.org wrote:
> > > > On Thu, 2019-05-30 at 02:02 +0300, Adrian Bunk wrote:
> > > So.. Can we have a bz and xz version built until thud is in
> > > community
> > > supported and update Warrior to use xz ?
> > 
> > I think thud and warrior will work fine if we backport just the
> > upgrade
> > and the change to uninative.bbclass?
> > 
> > I really don't want to try and do both.
> 
> To be honest, I'd really like to see thud/warrior keep the bz2 and
> master switch.  Changing underlying host dependencies especially ones
> that we hit on in special early threads seems like a bad idea.  I've
> been doing too many "fun" things in containers of late, and CROPS
> might be fine but bare Ubuntu containers aren't and this would be a
> very funky error to diagnose.  Given we've released I think we need
> to err on the side of consistency.

Whilst we could in theory start hacking around the infrastructure to
put dual tarballs in place, I'd really prefer not to be doing that for
uninative releases for the next 1-2 years.

xz appears to be documented as a host dependency even if it isn't in
HOSTTOOLS and isn't very obscure.

I can see both sides of this :/.

Cheers,

Richard