meta-openembedded/meta-filesystems
Andreas Müller 14c4d27bf0 Revert "physfs: move to sources found at github/supertux"
This reverts commit 3bbec2b792.

The commit was intended to make supertux in meta-games happy. Now I found out
that:

* other packets e.g meta-retro d1x-rebirth segfault with supertux version of physfs
* supertux can be configured to use it's own physfs as static library

To avoid package version counting backwards PE = 1 was added. The patch
required for supertux was already applied in meta-games.

Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
(cherry picked from commit c3dad0ba49)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2016-11-29 08:22:21 -08:00
..
conf meta-filesystems: Add LAYERVERSION and LAYERDEPENDS 2014-11-28 13:41:45 +01:00
recipes-filesystems yaffs2-utils: fix QA warning for GNU_HASH 2016-08-31 18:21:59 +02:00
recipes-support Revert "physfs: move to sources found at github/supertux" 2016-11-29 08:22:21 -08:00
recipes-utils xfsprogs, xfsdump, dmapi: blacklist, needs upgrade to stay compatible with default kernel 2016-10-03 19:19:54 +02:00
COPYING.MIT meta-filesystems creation 2013-08-16 12:58:31 +02:00
README meta-openembedded: Add me to morty maintainer's list 2016-11-15 15:14:32 +01:00

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/bitbake
  branch: morty

  URI: git://git.openembedded.org/openembedded-core
  layers: meta
  branch: morty

  URI: git://git.openembedded.org/meta-openembedded
  layers: meta-oe
  branch: morty

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.

Maintainers List:
  physfs      Andreas Müller <schnitzeltony@googlemail.com>

  fuse        Koen Kooi <koen@dominion.thruhere.net>
              Philip Balister <philip@balister.org>
              hongxu jia <hongxu.jia@windriver.com>

  ifuse       Sander van Grieken <sander@outrightsolutions.nl>
              Koen Kooi <koen@dominion.thruhere.net>

  sshfs-fuse  Philip Balister <philip@balister.org>
              Koen Kooi <koen@dominion.thruhere.net>

  owfs        Otavio Salvador <otavio@ossystems.com.br>
              Koen Kooi <koen@dominion.thruhere.net>
              hongxu jia <hongxu.jia@windriver.com>

  ntfs-3g-ntfsprogs  Otavio Salvador <otavio@ossystems.com.br>
                     hongxu jia <hongxu.jia@windriver.com>

  cramfs      Koen Kooi <koen@dominion.thruhere.net>

  smbnetfs    Sander van Grieken <sander@outrightsolutions.nl>
              Koen Kooi <koen@dominion.thruhere.net>

  fuse-exfat  hongxu jia <hongxu.jia@windriver.com>

  exfat-utils hongxu jia <hongxu.jia@windriver.com>

  f2fs-tools  Martin Jansa <Martin.Jansa@gmail.com>
              Koen Kooi <koen@dominion.thruhere.net>

  xfsprogs    Koen Kooi <koen@dominion.thruhere.net>
              hongxu jia <hongxu.jia@windriver.com>

When sending single patches, please use something like:

   git send-email -1 -M \
        --to openembedded-devel@lists.openembedded.org \
        --subject-prefix=meta-filesystems][morty][PATCH

morty branch maintainer(s):
Armin Kuster <akuster808@gmail.com>

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.