From: Ross Burton <Ross.Burton@arm.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>, nd <nd@arm.com>,
"bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Subject: Re: [OE-core] [PATCH 9/9] lzo: remove recipe from oe-core
Date: Wed, 25 May 2022 11:26:46 +0000 [thread overview]
Message-ID: <9BB79F38-1612-4383-BAE2-DD4FD065476B@arm.com> (raw)
In-Reply-To: <20220525100322.1a50d726@melee>
On 25 May 2022, at 09:03, Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
>
> Hi Ross, Bruce,
>
> Il giorno Tue, 24 May 2022 16:24:01 +0100
> "Ross Burton" <ross.burton@arm.com> ha scritto:
>
>> LZO is a fairly archaic compression format that hasn't been updated
>> since 2017. It's now unused by anything else in oe-core, so remove
>> the recipes.
>>
>> Signed-off-by: Ross Burton <ross.burton@arm.com>
>
> I love removals of archaic features...
>
> ...and how they make things explode :-)
>
> stdio: ERROR: Nothing PROVIDES 'lzo' (but
> /home/pokybuild/yocto-worker/meta-virt/build/meta-virtualization/recipes-extended/xen/xen_4.16.bb,
> /home/pokybuild/yocto-worker/meta-virt/build/meta-virtualization/recipes-extended/xen/xen-tools_4.16.bb
> DEPENDS on or otherwise requires it)
I’ve also just sent a RFC patch for xen to disable LZO entirely, but I’ll leave that up to Bruce to decide. If lzo is removed from core it will be added to meta-oe, so xen will continue to build either way.
Ross
next prev parent reply other threads:[~2022-05-25 11:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 15:23 [PATCH 1/9] lzo: Add further info to a patch Ross Burton
2022-05-24 15:23 ` [PATCH 2/9] btrfs-tools: add a PACKAGECONFIG for lzo Ross Burton
2022-05-24 15:23 ` [PATCH 3/9] mtd-utils: disable LZO by default Ross Burton
2022-05-25 9:33 ` [OE-core] " richard.purdie
2022-05-25 10:34 ` Ross Burton
2022-05-25 11:38 ` richard.purdie
2022-05-24 15:23 ` [PATCH 4/9] squashfs-tools: " Ross Burton
2022-05-24 15:23 ` [PATCH 5/9] libarchive: " Ross Burton
2022-05-24 15:23 ` [PATCH 6/9] lzop: remove recipe from oe-core Ross Burton
2022-05-24 15:23 ` [PATCH 7/9] oeqa/selftest/imagefeatures: don't exercise lzo compression Ross Burton
2022-05-24 15:24 ` [PATCH 8/9] packagegroup-self-hosted: remove lzo Ross Burton
2022-05-24 15:24 ` [PATCH 9/9] lzo: remove recipe from oe-core Ross Burton
2022-05-25 8:03 ` [OE-core] " Luca Ceresoli
2022-05-25 11:26 ` Ross Burton [this message]
2022-05-25 12:59 ` Bruce Ashfield
2022-05-25 13:45 ` Ross Burton
2022-05-25 13:55 ` Bruce Ashfield
2022-05-25 8:00 ` [OE-core] [PATCH 1/9] lzo: Add further info to a patch Luca Ceresoli
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=9BB79F38-1612-4383-BAE2-DD4FD065476B@arm.com \
--to=ross.burton@arm.com \
--cc=bruce.ashfield@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/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