Skip to contentSkip to conversation

fuse3: add libfuse3 recipe

PATCH In review Stefan Agner 3 participants 4 messages Sep 10, 2019 – Sep 11, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 fuse3: add libfuse3 recipe

From: Stefan Agner <[email protected]>

Add recipe for libfuse version 3 series. Follow the scheme other distributions use and create a new recipe with 3 in its name. To avoid conflict with the fuse (2) recipe this recipe does not provide init scripts/configuration files which automatically load the fuse kernel driver.

---
 .../recipes-support/fuse/fuse3_3.6.2.bb       | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 meta-filesystems/recipes-support/fuse/fuse3_3.6.2.bb
meta-filesystems/recipes-support/fuse/fuse3_3.6.2.bb new file +48 -0
new file mode 100644
index 000000000..e65eb08e2
@@ -0,0 +1,48 @@
+SUMMARY = "Implementation of a fully functional filesystem in a userspace program"
+DESCRIPTION = "FUSE (Filesystem in Userspace) is a simple interface for userspace \
+               programs to export a virtual filesystem to the Linux kernel. FUSE \
+               also aims to provide a secure method for non privileged users to \
+               create and mount their own filesystem implementations. \
+              "
+HOMEPAGE = "https://github.com/libfuse/libfuse"
+SECTION = "libs"
+LICENSE = "GPLv2 & LGPLv2"
+LIC_FILES_CHKSUM = "file://GPL2.txt;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
+                    file://LGPL2.txt;md5=4fbd65380cdd255951079008b364516c \
+                    file://LICENSE;md5=a55c12a2d7d742ecb41ca9ae0a6ddc66"
+
+SRC_URI = "https://github.com/libfuse/libfuse/releases/download/fuse-${PV}/fuse-${PV}.tar.xz \
+"
+SRC_URI[md5sum] = "1798945aa69434286723b9999a141c7a"
+SRC_URI[sha256sum] = "f45869427575e1e59ab743a67deb57addbf2cb8f9ce431199dbd40ddab71f281"
+
+S = "${WORKDIR}/fuse-${PV}"
+
+UPSTREAM_CHECK_URI = "https://github.com/libfuse/libfuse/releases"
+UPSTREAM_CHECK_REGEX = "fuse\-(?P<pver>3(\.\d+)+).tar.xz"
+
+inherit meson pkgconfig
+
+DEPENDS = "udev"
+
+PACKAGES =+ "fuse3-utils"
+
+RPROVIDES_${PN}-dbg += "fuse3-utils-dbg"
+
+RRECOMMENDS_${PN}_class-target = "kernel-module-fuse fuse3-utils"
+
+FILES_${PN} += "${libdir}/libfuse3.so.*"
+FILES_${PN}-dev += "${libdir}/libfuse3*.la"
+
+EXTRA_OEMESON += " \
+     -Dexamples=false \
+"
+
+# Forbid auto-renaming to libfuse3-utils
+FILES_fuse3-utils = "${bindir} ${base_sbindir}"
+DEBIAN_NOAUTONAME_fuse3-utils = "1"
+DEBIAN_NOAUTONAME_${PN}-dbg = "1"
+
+do_install_append() {
+    rm -rf ${D}${base_prefix}/dev
+}
Signature · 1 line
2.20.1
#1 lore raw

Stefan,

Quoted 9 lines · Stefan Agner

From: Stefan Agner <[email protected]>

Add recipe for libfuse version 3 series. Follow the scheme other distributions use and create a new recipe with 3 in its name. To avoid conflict with the fuse (2) recipe this recipe does not provide init scripts/configuration files which automatically load the fuse kernel driver.

This recipe appears to already exist in meta-filesystem

https://git.openembedded.org/meta-openembedded/tree/meta-filesystems/recipes-support/fuse/fuse_2.9.9.bb

Is this a all together a different Major version that is not compatible with the one above? or should we just update the old one?

- armin

Quoted 59 lines
---
 .../recipes-support/fuse/fuse3_3.6.2.bb       | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 meta-filesystems/recipes-support/fuse/fuse3_3.6.2.bb
meta-filesystems/recipes-support/fuse/fuse3_3.6.2.bb new file +48 -0
new file mode 100644
index 000000000..e65eb08e2
@@ -0,0 +1,48 @@
+SUMMARY = "Implementation of a fully functional filesystem in a userspace program"
+DESCRIPTION = "FUSE (Filesystem in Userspace) is a simple interface for userspace \
+               programs to export a virtual filesystem to the Linux kernel. FUSE \
+               also aims to provide a secure method for non privileged users to \
+               create and mount their own filesystem implementations. \
+              "
+HOMEPAGE = "https://github.com/libfuse/libfuse"
+SECTION = "libs"
+LICENSE = "GPLv2 & LGPLv2"
+LIC_FILES_CHKSUM = "file://GPL2.txt;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
+                    file://LGPL2.txt;md5=4fbd65380cdd255951079008b364516c \
+                    file://LICENSE;md5=a55c12a2d7d742ecb41ca9ae0a6ddc66"
+
+SRC_URI = "https://github.com/libfuse/libfuse/releases/download/fuse-${PV}/fuse-${PV}.tar.xz \
+"
+SRC_URI[md5sum] = "1798945aa69434286723b9999a141c7a"
+SRC_URI[sha256sum] = "f45869427575e1e59ab743a67deb57addbf2cb8f9ce431199dbd40ddab71f281"
+
+S = "${WORKDIR}/fuse-${PV}"
+
+UPSTREAM_CHECK_URI = "https://github.com/libfuse/libfuse/releases"
+UPSTREAM_CHECK_REGEX = "fuse\-(?P<pver>3(\.\d+)+).tar.xz"
+
+inherit meson pkgconfig
+
+DEPENDS = "udev"
+
+PACKAGES =+ "fuse3-utils"
+
+RPROVIDES_${PN}-dbg += "fuse3-utils-dbg"
+
+RRECOMMENDS_${PN}_class-target = "kernel-module-fuse fuse3-utils"
+
+FILES_${PN} += "${libdir}/libfuse3.so.*"
+FILES_${PN}-dev += "${libdir}/libfuse3*.la"
+
+EXTRA_OEMESON += " \
+     -Dexamples=false \
+"
+
+# Forbid auto-renaming to libfuse3-utils
+FILES_fuse3-utils = "${bindir} ${base_sbindir}"
+DEBIAN_NOAUTONAME_fuse3-utils = "1"
+DEBIAN_NOAUTONAME_${PN}-dbg = "1"
+
+do_install_append() {
+    rm -rf ${D}${base_prefix}/dev
+}
#2 lore raw

Hi Armin

Quoted 11 lines · On 9/10/19 3:06 PM, akuster808 wrote:

Stefan,

Quoted 8 lines · Stefan Agner

From: Stefan Agner <[email protected]>

Add recipe for libfuse version 3 series. Follow the scheme other distributions use and create a new recipe with 3 in its name. To avoid conflict with the fuse (2) recipe this recipe does not provide init scripts/configuration files which automatically load the fuse kernel driver.

Quoted 9 lines
Quoted 1 line

This recipe appears to already exist in meta-filesystem

https://git.openembedded.org/meta-openembedded/tree/meta-filesystems/recipes-support/fuse/fuse_2.9.9.bb

Is this a all together a different Major version that is not compatible with the one above? or should we just update the old one?

These are different revisions which can be installed together see [1]
I think best solution is as proposed where both revisions can live together, we don't want to force fuse2 users to fuse3 since it could mean quite a bit of unplanned work. Eventually we might drop fuse2 maybe in 3.1+ releases if all users of fuse in OE have moved over to fuse3

[1] https://github.com/libfuse/libfuse/blob/master/ChangeLog.rst#libfuse-300-2016-12-08

#3 lore raw
Quoted 24 lines · Khem Raj

Hi Armin

Quoted 11 lines · On 9/10/19 3:06 PM, akuster808 wrote:

Stefan,

Quoted 8 lines · Stefan Agner

From: Stefan Agner <[email protected]>

Add recipe for libfuse version 3 series. Follow the scheme other distributions use and create a new recipe with 3 in its name. To avoid conflict with the fuse (2) recipe this recipe does not provide init scripts/configuration files which automatically load the fuse kernel driver.

Quoted 9 lines
Quoted 1 line

This recipe appears to already exist in meta-filesystem

https://git.openembedded.org/meta-openembedded/tree/meta-filesystems/recipes-support/fuse/fuse_2.9.9.bb

Is this a all together a different Major version that is not compatible with the one above? or should we just update the old one?

Quoted 6 lines

These are different revisions which can be installed together see [1] I think best solution is as proposed where both revisions can live together, we don't want to force fuse2 users to fuse3 since it could mean quite a bit of unplanned work. Eventually we might drop fuse2 maybe in 3.1+ releases if all users of fuse in OE have moved over to fuse3

Yes, fuse3 seems to be a non backward compatible release. Lots of project still require fuse2. E.g. in ArchLinux you can see that actually most packages still depend on fuse2:
https://www.archlinux.org/packages/extra/x86_64/fuse2/
https://www.archlinux.org/packages/extra/x86_64/fuse3/

Given that so many projects still rely on fuse2, I guess dropping fuse2 will be even further out.

--
Stefan

Quoted 3 lines

[1]
https://github.com/libfuse/libfuse/blob/master/ChangeLog.rst#libfuse-300-2016-12-08