From: Stefan Agner <stefan@agner.ch>
To: Ross Burton <ross.burton@intel.com>
Cc: Stefan Agner <stefan.agner@toradex.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 1/2] zstd: move recipe to oe-core from meta-oe
Date: Mon, 18 Nov 2019 19:37:20 +0100 [thread overview]
Message-ID: <4beb1e7703a6733e81e62cfde8ca1531@agner.ch> (raw)
In-Reply-To: <eb8e027d-2797-4bce-a59d-e7e2eb369aa6@intel.com>
On 2019-11-18 17:53, Ross Burton wrote:
> On 18/11/2019 16:47, akuster808 wrote:
>> Does a possible Poky LTS have any factor in deciding to add more
>> packages to core?
>
> Even without the LTS there's a (relatively) long-term commitment to
> maintain recipes.
>
> Personally, I'm happy with Zstd being in meta-oe for now, and possibly
> re-evaluating in the next cycle.
Not having it in oe-core would mean we would have to exclude it from
build testing [1].
From what I can tell, that would be a first: Every other compression
conversion is part of oe-core.
It had quite some adoption lately, e.g. Fedora 31 uses zstd by default
to compress their rpm packages [2].
IMHO, this are good arguments for adding it to oe-core now.
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2019-November/288882.html
[2]
https://fedoraproject.org/wiki/Changes/Switch_RPMs_to_zstd_compression
--
Stefan
next prev parent reply other threads:[~2019-11-18 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 9:14 [PATCH v3 1/2] zstd: move recipe to oe-core from meta-oe Stefan Agner
2019-11-08 9:14 ` [PATCH v3 2/2] image_types: add Zstandard conversion support Stefan Agner
2019-11-14 14:47 ` [PATCH v3 1/2] zstd: move recipe to oe-core from meta-oe Stefan Agner
2019-11-18 12:19 ` Richard Purdie
2019-11-18 16:47 ` akuster808
2019-11-18 16:53 ` Ross Burton
2019-11-18 18:37 ` Stefan Agner [this message]
2019-11-18 18:39 ` Stefan Agner
2019-11-19 16:18 ` Alex Kiernan
2019-11-20 8:46 ` Stefan Agner
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=4beb1e7703a6733e81e62cfde8ca1531@agner.ch \
--to=stefan@agner.ch \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=stefan.agner@toradex.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 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.