From: Aatir Manzur <aatrapps@gmail.com>
To: docs@lists.yoctoproject.org
Cc: Aatir Manzur <aatrapps@gmail.com>
Subject: [PATCH] docs: Sphinx note directive for DISTO_FEATURES definition
Date: Tue, 5 Jul 2022 15:38:47 -0400 [thread overview]
Message-ID: <20220705193847.12544-1-aatrapps@gmail.com> (raw)
Signed-off-by: Aatir Manzur <aatrapps@gmail.com>
---
documentation/ref-manual/variables.rst | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index c4b2119f2..6a43e8dc5 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1886,10 +1886,14 @@ system and gives an overview of their function and contents.
optionally support the feature. For example, specifying "x11" in
:term:`DISTRO_FEATURES`, causes every piece of software built for the
target that can optionally support X11 to have its X11 support
- enabled. Note: just enabling :term:`DISTRO_FEATURES` alone doesn't
- enable feature support for packages, mechanisms such as making
- :term:`PACKAGECONFIG` track :term:`DISTRO_FEATURES` are used
- to enable/disable package features.
+ enabled.
+
+ .. note::
+
+ Just enabling :term:`DISTRO_FEATURES` alone doesn't
+ enable feature support for packages. Mechanisms such as making
+ :term:`PACKAGECONFIG` track :term:`DISTRO_FEATURES` are used
+ to enable/disable package features.
Two more examples are Bluetooth and NFS support. For a more complete
list of features that ships with the Yocto Project and that you can
--
2.25.1
next reply other threads:[~2022-07-05 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:38 Aatir Manzur [this message]
2022-07-18 9:06 ` [docs] [PATCH] docs: Sphinx note directive for DISTO_FEATURES definition Quentin Schulz
[not found] ` <d5241899-8670-dbad-1872-5f6da520b061@bootlin.com>
2022-07-18 11:33 ` Aatir Manzur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220705193847.12544-1-aatrapps@gmail.com \
--to=aatrapps@gmail.com \
--cc=docs@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox