From: Adrian Bunk <bunk@stusta.de>
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] uninative: Switch from bz2 to xz
Date: Thu, 30 May 2019 02:02:03 +0300 [thread overview]
Message-ID: <20190529230203.GB16075@localhost> (raw)
In-Reply-To: <20190529222920.GP20781@bill-the-cat>
On Wed, May 29, 2019 at 06:29:20PM -0400, Tom Rini wrote:
> On Thu, May 30, 2019 at 01:17:26AM +0300, Adrian Bunk wrote:
> > On Wed, May 29, 2019 at 10:29:31PM +0100, richard.purdie@linuxfoundation.org wrote:
> > > On Wed, 2019-05-29 at 17:25 -0400, Tom Rini wrote:
> > > > On Wed, May 29, 2019 at 09:50:22PM +0100,
> > > > richard.purdie@linuxfoundation.org wrote:
> > > > > On Wed, 2019-05-29 at 13:39 -0700, akuster808 wrote:
> > > > > > On 5/29/19 12:26 PM, richard.purdie@linuxfoundation.org wrote:
> > > > > > > On Wed, 2019-05-29 at 12:21 -0700, akuster808 wrote:
> > > > > > > > On 5/29/19 11:43 AM, Richard Purdie wrote:
> > > > > > > > > (From OE-Core rev:
> > > > > > > > > 29fc9210b973be68de474e75068e4c72371afe5a)
> > > > > > > > >
> > > > > > > > > Signed-off-by: Richard Purdie <
> > > > > > > > > richard.purdie@linuxfoundation.org>
> > > > > > > > With back port to warrior and Thud too?
> > > > > > > Yes, we'll need to do that if we bring fedora 30 workers online
> > > > > > > on
> > > > > > > the
> > > > > > > autobuilder.
> > > > > > I know the uninative update is required for FC30 but changing the
> > > > > > compression does not.
> > > > > >
> > > > > > This question is about the compression extension question.
> > > > > >
> > > > > > Does this mean YP will no longer be providing bz2 uninatives?
> > > > >
> > > > > Correct, the patch should be straight forward to include with the
> > > > > upgrade.
> > > >
> > > > Does that in turn mean we must have host xz-utils?
> > >
> > > It will mean you need a tar which supports the -J option. The tests
> > > I've see so far suggest all our oldest supported distros do...
> >
> > For thud tar >= 1.27 is required, -J was added in 1.22.
> >
> > But Tom is asking about something different:
> > tar calls "xz -d" for decompression, which needs xz-utils installed.
> >
> > https://www.yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#required-packages-for-the-build-host
> > documents that xz has to be installed, but looking at
> > meta/conf/bitbake.conf it might be missing in HOSTTOOLS.
>
> I think it's also missing in for example the crops containers. So if
> we're going to backport it, I think maybe we should keep it bz2? The
> size difference can't be that much.
The size difference is surprisingly high - a factor of 5 (sic).
But in practice the difference between 5 MB and 26 MB
shouldn't really matter.
> Tom
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-05-29 23:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 18:43 [PATCH 1/2] yocto-uninative: Update to 2.5 release Richard Purdie
2019-05-29 18:43 ` [PATCH 2/2] uninative: Switch from bz2 to xz Richard Purdie
2019-05-29 19:21 ` akuster808
2019-05-29 19:26 ` richard.purdie
2019-05-29 20:39 ` akuster808
2019-05-29 20:50 ` richard.purdie
2019-05-29 21:25 ` Tom Rini
2019-05-29 21:29 ` richard.purdie
2019-05-29 22:17 ` Adrian Bunk
2019-05-29 22:29 ` Tom Rini
2019-05-29 23:02 ` Adrian Bunk [this message]
2019-05-30 8:13 ` richard.purdie
2019-05-30 13:32 ` akuster808
2019-05-30 13:55 ` richard.purdie
2019-05-30 15:57 ` Tom Rini
2019-05-31 13:44 ` richard.purdie
2019-05-30 13:59 ` Adrian Bunk
2019-05-30 14:06 ` richard.purdie
2019-05-30 14:25 ` Adrian Bunk
2019-05-30 14:15 ` akuster808
2019-05-30 2:54 ` Tim Orling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190529230203.GB16075@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=trini@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox