e49860ee21
* add Pending to .patch files where it was accidentally droped with upgrades or modifications in: f88e5b146e postgresql: upgrade 15.5 -> 16.2 c904e169db multipath-tools: upgrade 0.9.3 -> 0.9.8 105be9b3d9 unionfs-fuse: upgrade 2.2 --> 3.4 or new patches where the author didn't notice/care: 2a7f74cdb0 dropwatch: Use header files from sysroot instead of build host f5cc9f272a yasm: improve reproducibility 39028d0d9d python3-pybind11: Restore strip prevention patch authors of these added to CC, please be more careful with removing or not adding these or enable patch-status in ERROR_QA for your builds, see: https://lists.openembedded.org/g/openembedded-core/topic/104922136#197113 * added with: for p in `/OE/layers/openembedded-core/scripts/contrib/patchreview.py -v . | grep Missing.Upstream-Status.tag | sed 's/.*(//g;s/)$//g'`; do grep -q ^Upstream-Status: $p || sed -i "s/^---$/\nUpstream-Status: Pending\n---/g" $p; grep -q ^Upstream-Status: $p || sed -i "1iUpstream-Status: Pending\n" $p; done Signed-off-by: Martin Jansa <martin.jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
This README file contains information on the contents of the filesystems layer.
Please see the corresponding sections below for details.
Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core layers: meta branch: master
URI: git://git.openembedded.org/meta-openembedded layers: meta-oe branch: master
Patches
Please submit any patches against the filesystems layer to the OpenEmbedded development mailing list (openembedded-devel@lists.openembedded.org) with '[meta-filesystems]' in the subject.
Layer maintainer: Khem Raj raj.khem@gmail.com
When sending single patches, please use something like:
git send-email -1 -M
--to openembedded-devel@lists.openembedded.org
--subject-prefix='meta-filesystems][PATCH'
Table of Contents
I. Adding the filesystems layer to your build II. Misc
I. Adding the filesystems layer to your build
In order to use this layer, you need to make the build system aware of it.
Assuming the filesystems layer exists at the top-level of your yocto build tree, you can add it to the build system by adding the location of the filesystems layer to bblayers.conf, along with any other layers needed. e.g.:
BBLAYERS ?= "
/path/to/yocto/meta
/path/to/yocto/meta-oe
/path/to/yocto/meta-filesystems
"
II. Misc
--- physfs --- A library to provide abstract access to various archives
--- fuse --- Filesystem in Userspace (FUSE) is a simple interface for userspace programs to export a virtual filesystem to the Linux kernel.
--- ifuse --- A fuse filesystem to access the contents of an iPhone or iPod Touch
--- sshfs-fuse --- A filesystem client based on the SSH File Transfer Protocol
--- owfs --- An easy way to use the 1-Wire file system
--- ntfs-3g-ntfsprogs --- The ntfs-3g is a freely available read/write NTFS driver for Linux and ntfsprogs includes utilities for doing all required tasks to NTFS partitions.
--- cramfs --- Builds cramfs filesystems for embedded systems
--- smbnetfs --- SMBNetFS is a Linux/FreeBSD filesystem that allow you to use samba/microsoft network in the same manner as the network neighborhood in Microsoft Windows.
--- fuse-exfat --- A read and write exFAT driver for FUSE
--- exfat-utils --- Utilities to create, check, label and dump exFAT filesystem
--- f2fs-tools --- Tools needed for creating and managing f2fs partitions
--- xfsprogs --- It provides XFS filesystem utilities.