mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-16 18:49:34 +02:00
Code Issues Packages Projects Releases Wiki Activity

overview-manual: remove confusing and unnecessary paragraph about site.conf

Browse Source 
The explanations which precede and follow are sufficient.

The removed text seemed to suggest to use conf/site.conf to specify
the location of another conf/site.conf file.

Another issue was that the way to override conf/site.conf settings
through conf/local.conf was described before explaining that
conf/site.conf is processed before conf/local.conf.

(From yocto-docs rev: d477a2044e7b53977daf4d0c0d45cad29c2006fb)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2022-04-26 19:44:20 +02:00
committed by Richard Purdie
parent 76ae677313
commit 771d574a40
1 changed files with 2 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
documentation/overview-manual/concepts.rst
View File

@@ -313,7 +313,7 @@ section in the Yocto Project Development Tasks Manual.
The files ``site.conf`` and ``auto.conf`` are not created by the The files ``site.conf`` and ``auto.conf`` are not created by the
environment initialization script. If you want the ``site.conf`` file, environment initialization script. If you want the ``site.conf`` file,
you need to create that yourself. The ``auto.conf`` file is typically you need to create it yourself. The ``auto.conf`` file is typically
created by an autobuilder: created by an autobuilder:
- *site.conf:* You can use the ``conf/site.conf`` configuration - *site.conf:* You can use the ``conf/site.conf`` configuration
@@ -321,17 +321,7 @@ created by an autobuilder:
you had several build environments and they shared some common you had several build environments and they shared some common
features. You can set these default build properties here. A good features. You can set these default build properties here. A good
example is perhaps the packaging format to use through the example is perhaps the packaging format to use through the
:term:`PACKAGE_CLASSES` :term:`PACKAGE_CLASSES` variable.
variable.
One useful scenario for using the ``conf/site.conf`` file is to
extend your :term:`BBPATH` variable
to include the path to a ``conf/site.conf``. Then, when BitBake looks
for Metadata using :term:`BBPATH`, it finds the ``conf/site.conf`` file
and applies your common configurations found in the file. To override
configurations in a particular build directory, alter the similar
configurations within that build directory's ``conf/local.conf``
file.
- *auto.conf:* The file is usually created and written to by an - *auto.conf:* The file is usually created and written to by an
autobuilder. The settings put into the file are typically the same as autobuilder. The settings put into the file are typically the same as