From: Jose Quaresma <quaresma.jose@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jose Quaresma <jose.quaresma@foundries.io>
Subject: [oe][master][scarthgap][PATCH 1/5] composefs: remove fuse3 dependencie
Date: Thu, 9 May 2024 10:31:22 +0100 [thread overview]
Message-ID: <20240509093126.503764-1-jose.quaresma@foundries.io> (raw)
The fuse3 is only used for development purposes and the composefs uses
the kernel overlayfs and erofs on the target.
The composefs-fuse [1] tool is not even installed by default
So all the files installed on the target are the same
with and without the fuse, this can be checked with buildhistory.
[1] https://github.com/containers/composefs/commit/f5fed9ff093ac57967a4c5253bae3ae294dd8cd9
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
---
meta-filesystems/recipes-support/composefs/composefs_1.0.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-filesystems/recipes-support/composefs/composefs_1.0.3.bb b/meta-filesystems/recipes-support/composefs/composefs_1.0.3.bb
index 7607b0a12..98eb3e1b3 100644
--- a/meta-filesystems/recipes-support/composefs/composefs_1.0.3.bb
+++ b/meta-filesystems/recipes-support/composefs/composefs_1.0.3.bb
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "\
file://COPYINGv3;md5=d32239bcb673463ab874e80d47fae504 \
file://LICENSE.Apache-2.0;md5=3b83ef96387f14655fc854ddc3c6bd57 \
"
-DEPENDS = "fuse3 openssl"
+DEPENDS = "openssl"
SRCREV = "2d5cdcb9176cfe4ccf1761ef6d78e1c48de35649"
PV = "1.0.3"
--
2.45.0
next reply other threads:[~2024-05-09 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 9:31 Jose Quaresma [this message]
2024-05-09 9:31 ` [oe][master][scarthgap][PATCH 2/5] composefs: move from meta-filesystems to meta-oe layer Jose Quaresma
2024-05-09 9:31 ` [oe][master][scarthgap][PATCH 3/5] composefs: refactor Jose Quaresma
2024-05-09 9:31 ` [oe][master][scarthgap][PATCH 4/5] composefs: bump ecef20c1 Jose Quaresma
2024-05-09 9:31 ` [oe][master][scarthgap][PATCH 5/5] composefs: add native target support Jose Quaresma
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=20240509093126.503764-1-jose.quaresma@foundries.io \
--to=quaresma.jose@gmail.com \
--cc=jose.quaresma@foundries.io \
--cc=openembedded-devel@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;
as well as URLs for NNTP newsgroup(s).