From: Alex Stewart <alex.stewart@ni.com>
To: ecordonnier@snapchat.com, openembedded-core@lists.openembedded.org
Cc: Etienne Cordonnier <ecordonnier@snap.com>,
Alex Feinman <afeinman@snap.com>
Subject: Re: [OE-core] [PATCH] opkg: enable zstd support
Date: Tue, 13 Sep 2022 14:19:19 -0500 [thread overview]
Message-ID: <a29c5799-9964-526d-d9e3-6a4f28cb1bc3@ni.com> (raw)
In-Reply-To: <20220913123741.3416807-1-ecordonnier@snap.com>
ACK from me - apart from enabling zstd by default.
On 9/13/22 07:37, Etienne Cordonnier via lists.openembedded.org wrote:
> This allows the use of zstd for opkg packages by using OPKGBUILDCMD:
> OPKGBUILDCMD = "opkg-build -Z zstd"
>
> Signed-off-by: Alex Feinman <afeinman@snap.com>
> Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
> ---
> meta/recipes-devtools/opkg/opkg_0.6.0.bb | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/opkg/opkg_0.6.0.bb b/meta/recipes-devtools/opkg/opkg_0.6.0.bb
> index 7b351e8123..e38d9d6f3f 100644
> --- a/meta/recipes-devtools/opkg/opkg_0.6.0.bb
> +++ b/meta/recipes-devtools/opkg/opkg_0.6.0.bb
> @@ -30,7 +30,7 @@ inherit autotools pkgconfig ptest
> target_localstatedir := "${localstatedir}"
> OPKGLIBDIR ??= "${target_localstatedir}/lib"
>
> -PACKAGECONFIG ??= "libsolv"
> +PACKAGECONFIG ??= "libsolv zstd"
Building in zstd support by default is a little suspect to me.
Unless I'm mistaken, OE-core will only build xz-compressed IPKs by
default. So zstd support would be unnecessary for a distro integrator
who just uses upstream OE-core.
For distros which use zstd compression in their packages, I think it
would be more appropriate to overwrite the opkg PACKAGECONFIG in a
.bbappend.
Is there something I'm not considering here?
>
> PACKAGECONFIG[gpg] = "--enable-gpg,--disable-gpg,\
> gnupg gpgme libgpg-error,\
> @@ -39,6 +39,7 @@ PACKAGECONFIG[gpg] = "--enable-gpg,--disable-gpg,\
> PACKAGECONFIG[curl] = "--enable-curl,--disable-curl,curl"
> PACKAGECONFIG[ssl-curl] = "--enable-ssl-curl,--disable-ssl-curl,curl openssl"
> PACKAGECONFIG[sha256] = "--enable-sha256,--disable-sha256"
> +PACKAGECONFIG[zstd] = "--enable-zstd,--disable-zstd,zstd"
> PACKAGECONFIG[libsolv] = "--with-libsolv,--without-libsolv,libsolv"
>
> EXTRA_OECONF:class-native = "--localstatedir=/${@os.path.relpath('${localstatedir}', '${STAGING_DIR_NATIVE}')} --sysconfdir=/${@os.path.relpath('${sysconfdir}', '${STAGING_DIR_NATIVE}')}"
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#170575): https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/message/170575__;!!FbZ0ZwI3Qg!pogpLkfpLwPy4zdzhTDEFkMT6eNuynfXzyaNvTq4OK74eYha04b285qGN5bk1t7aQmJAqnSBddI6-TD8FLOtzgtG_5PjNUviztKz$
> Mute This Topic: https://urldefense.com/v3/__https://lists.openembedded.org/mt/93654146/3616788__;!!FbZ0ZwI3Qg!pogpLkfpLwPy4zdzhTDEFkMT6eNuynfXzyaNvTq4OK74eYha04b285qGN5bk1t7aQmJAqnSBddI6-TD8FLOtzgtG_5PjNVdoKO7n$
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://urldefense.com/v3/__https://lists.openembedded.org/g/openembedded-core/unsub__;!!FbZ0ZwI3Qg!pogpLkfpLwPy4zdzhTDEFkMT6eNuynfXzyaNvTq4OK74eYha04b285qGN5bk1t7aQmJAqnSBddI6-TD8FLOtzgtG_5PjNfNktoah$ [alex.stewart@ni.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)
alex.stewart@ni.com
next prev parent reply other threads:[~2022-09-13 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 12:37 [PATCH] opkg: enable zstd support Etienne Cordonnier
2022-09-13 19:19 ` Alex Stewart [this message]
2022-09-13 19:42 ` [OE-core] " Khem Raj
[not found] ` <CANOoYsMVb9YpfwjTNHv4kSARM15_3T34CA-Ekr=t7P5F0XO4bA@mail.gmail.com>
2022-09-13 20:24 ` Alex Feinman
2022-09-13 20:34 ` Khem Raj
2022-09-13 21:57 ` Alex Stewart
2022-09-14 9:58 ` Etienne Cordonnier
2022-09-14 10:08 ` Etienne Cordonnier
2022-09-14 15:37 ` Alex Stewart
2022-09-14 15:41 ` Khem Raj
2022-09-28 16:50 ` Etienne Cordonnier
2022-09-28 18:03 ` Alex Stewart
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=a29c5799-9964-526d-d9e3-6a4f28cb1bc3@ni.com \
--to=alex.stewart@ni.com \
--cc=afeinman@snap.com \
--cc=ecordonnier@snap.com \
--cc=ecordonnier@snapchat.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 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.