All of lore.kernel.org
 help / color / mirror / Atom feed
From: raphael.melotte at essensium.com <raphael.melotte@essensium.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] docs/manual/adding-packages-python.txt: fix outdated Python 3 sentence.
Date: Mon,  9 Sep 2019 13:58:07 +0200	[thread overview]
Message-ID: <20190909115807.5753-1-raphael.melotte@essensium.com> (raw)

From: Rapha?l M?lotte <raphael.melotte@essensium.com>

Python packages should no longer depend on BR2_PACKAGE_PYTHON
in their config file, unless they are only compatible with Python 2.

Signed-off-by: Rapha?l M?lotte <raphael.melotte@essensium.com>
---
 docs/manual/adding-packages-python.txt | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/docs/manual/adding-packages-python.txt b/docs/manual/adding-packages-python.txt
index 15137cfd6d..74e2e78b29 100644
--- a/docs/manual/adding-packages-python.txt
+++ b/docs/manual/adding-packages-python.txt
@@ -67,9 +67,13 @@ Python build system, but are not Python modules, can freely choose
 their name (existing examples in Buildroot are +scons+ and
 +supervisor+).
 
-In their +Config.in+ file, they should depend on +BR2_PACKAGE_PYTHON+
-so that when Buildroot will enable Python 3 usage for modules, we will
-be able to enable Python modules progressively on Python 3.
+Packages that are only compatible with one version of Python (as in:
+Python 2 or Python 3) should depend on that version explicitely in
+their +Config.in+ file (+BR2_PACKAGE_PYTHON+ for Python 2,
++BR2_PACKAGE_PYTHON3+ for Python 3).  Packages that are compatible
+with both versions should not explicitely depend on them in their
++Config.in+ file, since that condition is already expressed for the
+whole "External python modules" menu.
 
 The main macro of the Python package infrastructure is
 +python-package+. It is similar to the +generic-package+ macro. It is
-- 
2.21.0

             reply	other threads:[~2019-09-09 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09 11:58 raphael.melotte at essensium.com [this message]
2019-09-10 17:29 ` [Buildroot] [PATCH 1/1] docs/manual/adding-packages-python.txt: fix outdated Python 3 sentence Thomas Petazzoni
2019-09-24 14:32 ` Peter Korsgaard

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=20190909115807.5753-1-raphael.melotte@essensium.com \
    --to=raphael.melotte@essensium.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.