From: richard.purdie@linuxfoundation.org
To: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Cc: "Søren Andersen" <san@skov.dk>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] squashfs-tools: upgrade to commit f95864afe883
Date: Wed, 17 Jul 2019 11:57:42 +0100 [thread overview]
Message-ID: <5fc8a130cfb17be80c146dec31ab5ffd71eea247.camel@linuxfoundation.org> (raw)
In-Reply-To: <6rlfwx2atq.fsf@pengutronix.de>
On Wed, 2019-07-17 at 12:51 +0200, Ulrich Ölmann wrote:
> Hi Richard,
>
> On Wed, Jul 17 2019 at 11:19 +0200, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2019-07-16 at 15:54 +0200, Ulrich Ölmann wrote:
> > > [...]
> > > -PACKAGECONFIG ??= "gzip xz lzo lz4 lzma xattr"
> > > +PACKAGECONFIG ??= "gzip xz lzo lz4 lzma xattr zstd reproducible"
> > > [...]
> > > +PACKAGECONFIG[zstd] = "ZSTD_SUPPORT=1,ZSTD_SUPPORT=0,zstd"
> > > +PACKAGECONFIG[reproducible] =
> > > "REPRODUCIBLE_DEFAULT=1,REPRODUCIBLE_DEFAULT=0,"
> >
> > This fails in OE-Core since zstd isn't present and you've enabled
> > that
> > by default:
> >
> > e.g.:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/827
> >
> > (but many other similar failures).
> >
> > Adding the PACKAGECONFIG[zstd] is good, we just can't enable it by
> > default.
>
> see my reply to Adrian: what do you think of transplanting the zstd
> recipe from meta-rauc to OE-core?
I think right now that zstd is not common enough to be something for
oe-core. If multiple people reply and disagree I'm willing to reasses
that but that's my feeling right now...
Cheers,
Richard
next prev parent reply other threads:[~2019-07-17 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 13:54 [PATCH] squashfs-tools: upgrade to commit f95864afe883 Ulrich Ölmann
2019-07-17 9:08 ` Adrian Bunk
2019-07-17 10:48 ` Ulrich Ölmann
2019-07-17 9:19 ` Richard Purdie
2019-07-17 10:51 ` Ulrich Ölmann
2019-07-17 10:57 ` richard.purdie [this message]
2019-07-18 6:19 ` Adrian Bunk
2019-07-18 11:13 ` Ulrich Ölmann
2019-07-19 12:22 ` Alex Kiernan
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=5fc8a130cfb17be80c146dec31ab5ffd71eea247.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=san@skov.dk \
--cc=u.oelmann@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.