From: Khem Raj <raj.khem@gmail.com>
To: docs@lists.yoctoproject.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH] docs: Remove PYTHON_PN from reference
Date: Wed, 21 Feb 2024 15:02:57 -0800 [thread overview]
Message-ID: <20240221230257.3551066-1-raj.khem@gmail.com> (raw)
PYTHON_PN is on its way out, therefore its good to remove it from
documentation so its used is not promoted anymore.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
documentation/ref-manual/variables.rst | 14 --------------
1 file changed, 14 deletions(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 6f7d6ff01ee..b319753445b 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -6813,20 +6813,6 @@ system and gives an overview of their function and contents.
names used when installing the Python headers and libraries in
sysroot (e.g. ``.../python3.3m/...``).
- :term:`PYTHON_PN`
- When used by recipes that inherit the :ref:`ref-classes-setuptools3`
- class, specifies the major Python version being built. For Python 3.x,
- :term:`PYTHON_PN` would be "python3". You do not have to set this
- variable as the OpenEmbedded build system automatically sets it for you.
-
- The variable allows recipes to use common infrastructure such as the
- following::
-
- DEPENDS += "${PYTHON_PN}-native"
-
- In the previous example,
- the version of the dependency is :term:`PYTHON_PN`.
-
:term:`QA_EMPTY_DIRS`
Specifies a list of directories that are expected to be empty when
packaging; if ``empty-dirs`` appears in :term:`ERROR_QA` or
--
2.43.2
next reply other threads:[~2024-02-21 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 23:02 Khem Raj [this message]
2024-02-22 12:57 ` [docs] [PATCH] docs: Remove PYTHON_PN from reference Michael Opdenacker
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=20240221230257.3551066-1-raj.khem@gmail.com \
--to=raj.khem@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).