From 771d574a40ec8be32b5af9c031bddcaa2001716a Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Tue, 26 Apr 2022 19:44:20 +0200 Subject: overview-manual: remove confusing and unnecessary paragraph about site.conf 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 Signed-off-by: Richard Purdie --- documentation/overview-manual/concepts.rst | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst index 7b056acc87..93437856d9 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst @@ -313,7 +313,7 @@ section in the Yocto Project Development Tasks Manual. The files ``site.conf`` and ``auto.conf`` are not created by the 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: - *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 features. You can set these default build properties here. A good example is perhaps the packaging format to use through the - :term:`PACKAGE_CLASSES` - 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. + :term:`PACKAGE_CLASSES` variable. - *auto.conf:* The file is usually created and written to by an autobuilder. The settings put into the file are typically the same as -- cgit v1.2.3-54-g00ecf