public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Piotr Łobacz" <p.lobacz@welotec.com>
To: openembedded-core@lists.openembedded.org
Cc: "Piotr Łobacz" <p.lobacz@welotec.com>
Subject: [OE-core][kirkstone][PATCH v2 2/4] libarchive: remove acls, xattr for target only
Date: Mon,  3 Apr 2023 14:24:07 +0200	[thread overview]
Message-ID: <20230403122409.3067997-2-p.lobacz@welotec.com> (raw)
In-Reply-To: <20230403122409.3067997-1-p.lobacz@welotec.com>

Libarchive is being used by OPKG package manager as default
API for extracting tar files. This fix allows us to extract
ipks packages with preserved ACLs and xattrs.

Fixes: [YOCTO #15091]

Signed-off-by: Piotr Łobacz <p.lobacz@welotec.com>
---
 meta/recipes-extended/libarchive/libarchive_3.6.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/libarchive/libarchive_3.6.2.bb b/meta/recipes-extended/libarchive/libarchive_3.6.2.bb
index acc84de9da..15b1a88ce9 100644
--- a/meta/recipes-extended/libarchive/libarchive_3.6.2.bb
+++ b/meta/recipes-extended/libarchive/libarchive_3.6.2.bb
@@ -9,7 +9,7 @@ DEPENDS = "e2fsprogs-native"
 
 PACKAGECONFIG ?= "zlib bz2 xz lzo zstd"
 
-PACKAGECONFIG:append:class-target = "\
+PACKAGECONFIG:append = "\
 	${@bb.utils.filter('DISTRO_FEATURES', 'acl xattr', d)} \
 "
 
-- 
2.34.1



  reply	other threads:[~2023-04-03 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 12:24 [OE-core][kirkstone][PATCH v2 1/4] package.bbclase: Add ACLs and xattrs to perform_packagecopy Piotr Łobacz
2023-04-03 12:24 ` Piotr Łobacz [this message]
2023-04-03 12:24 ` [OE-core][kirkstone][PATCH v2 3/4] opkg_archive: support ACLs, extended flags and attributes Piotr Łobacz
2023-04-03 12:24 ` [OE-core][kirkstone][PATCH v2 4/4] opkg-build: support ACLs and extended attributes Piotr Łobacz
2023-04-03 13:32 ` [OE-core][kirkstone][PATCH v2 1/4] package.bbclase: Add ACLs and xattrs to perform_packagecopy Richard Purdie

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=20230403122409.3067997-2-p.lobacz@welotec.com \
    --to=p.lobacz@welotec.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