Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: openembedded-core@lists.openembedded.org, "Søren Andersen" <san@skov.dk>
Subject: Re: [PATCH] squashfs-tools: upgrade to commit f95864afe883
Date: Thu, 18 Jul 2019 13:13:22 +0200	[thread overview]
Message-ID: <6rk1cf7fzh.fsf@pengutronix.de> (raw)
In-Reply-To: <20190718061948.GB27459@localhost>

On Thu, Jul 18 2019 at 08:19 +0200, Adrian Bunk <bunk@stusta.de> wrote:
> On Wed, Jul 17, 2019 at 11:57:42AM +0100, richard.purdie@linuxfoundation.org wrote:
>> 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...
>
> zstd not even being in meta-oe is a surprise that should be corrected.
>
> btrfs-tools would be the only user that comes immediately into my mind,
> but zstd support in the kernel btrfs driver is relatively new and not
> yet widely used.
>
> zstd has already gotten a lot of traction in the Open Source world,
> but regarding adding it to oe-core right now one could argue either way.

Nobody stood up and objected in the last 24h, so I will send a v2 that
simply drops "zstd" from the set of default options and refers to
meta-rauc's recipe.

>> Cheers,
>> 
>> Richard
>
> cu
> Adrian

Best regards
Ulrich
-- 
Pengutronix e.K.                           | Ulrich Ölmann               |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2019-07-18 11:13 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
2019-07-18  6:19       ` Adrian Bunk
2019-07-18 11:13         ` Ulrich Ölmann [this message]
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=6rk1cf7fzh.fsf@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=san@skov.dk \
    /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