diff options
author | Andrew Geissler <geissonator@yahoo.com> | 2021-02-13 00:55:30 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2021-02-25 23:15:06 +0300 |
commit | 706d5aacd7ab7b37c00df1a1b210e4ced06119e1 (patch) | |
tree | ed0bec373424d01accfb2e9c895c177a3e2d7abe /poky/documentation/overview-manual/concepts.rst | |
parent | ac970dd705934286df062e0f1501f776dc2ef01d (diff) | |
download | openbmc-706d5aacd7ab7b37c00df1a1b210e4ced06119e1.tar.xz |
Reset poky to before our libpam hacks
Things got a bit out of synch with openbmc-config due to the libpam
issues and the migration from the meta-* layers.
Revert the two previous commits and then put the latest poky in with the
libpam revert and get openbmc-config right again.
Revert "Revert "libpam: update 1.3.1 -> 1.5.1""
This reverts commit 87ddd3eab4df68e624b5350ccaab28b3b97547c0.
Revert "poky: subtree update:796be0593a..10c69538c0"
This reverts commit c723b72979bfac6362509cf1fe086900f6641f28.
Change-Id: I3a1f405193aee6a21fe0cd24be9927c143a23d9a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'poky/documentation/overview-manual/concepts.rst')
-rw-r--r-- | poky/documentation/overview-manual/concepts.rst | 28 |
1 files changed, 17 insertions, 11 deletions
diff --git a/poky/documentation/overview-manual/concepts.rst b/poky/documentation/overview-manual/concepts.rst index 257de44ec..8fbbabbac 100644 --- a/poky/documentation/overview-manual/concepts.rst +++ b/poky/documentation/overview-manual/concepts.rst @@ -141,10 +141,12 @@ hardware-specific configurations allows you to share other metadata by using a different layer where that metadata might be common across several pieces of hardware. -Many layers exist that work in the Yocto Project development environment. The -:yocto_home:`Yocto Project Curated Layer Index </software-overview/layers/>` -and :oe_layerindex:`OpenEmbedded Layer Index <>` both contain layers from -which you can use or leverage. +Many layers exist that work in the Yocto Project development +environment. The `Yocto Project Curated Layer +Index <https://www.yoctoproject.org/software-overview/layers/>`__ +and `OpenEmbedded Layer +Index <http://layers.openembedded.org/layerindex/branch/master/layers/>`__ +both contain layers from which you can use or leverage. By convention, layers in the Yocto Project follow a specific form. Conforming to a known structure allows BitBake to make assumptions @@ -378,11 +380,13 @@ figure <#general-workflow-figure>`__: - *Metadata (.bb + Patches):* Software layers containing user-supplied recipe files, patches, and append files. A good example - of a software layer might be the :oe_layer:`meta-qt5 layer </meta-qt5>` - from the :oe_layerindex:`OpenEmbedded Layer Index <>`. This layer is for - version 5.0 of the popular `Qt <https://wiki.qt.io/About_Qt>`__ - cross-platform application development framework for desktop, embedded and - mobile. + of a software layer might be the + `meta-qt5 layer <https://github.com/meta-qt5/meta-qt5>`__ from + the `OpenEmbedded Layer + Index <http://layers.openembedded.org/layerindex/branch/master/layers/>`__. + This layer is for version 5.0 of the popular + `Qt <https://wiki.qt.io/About_Qt>`__ cross-platform application + development framework for desktop, embedded and mobile. - *Machine BSP Configuration:* Board Support Package (BSP) layers (i.e. "BSP Layer" in the following figure) providing machine-specific @@ -2092,8 +2096,10 @@ The capability to run tasks in a fake root environment is known as the BitBake keyword/variable flag that requests a fake root environment for a task. -In the :term:`OpenEmbedded Build System`, the program that implements -fakeroot is known as :yocto_home:`Pseudo </software-item/pseudo/>`. Pseudo +In the :term:`OpenEmbedded Build System`, +the program that +implements fakeroot is known as +`Pseudo <https://www.yoctoproject.org/software-item/pseudo/>`__. Pseudo overrides system calls by using the environment variable ``LD_PRELOAD``, which results in the illusion of running as root. To keep track of "fake" file ownership and permissions resulting from operations that |