All of lore.kernel.org
 help / color / mirror / Atom feed
From: yegorslists at googlemail.com <yegorslists@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] scanpypi: rework runtime dependency handling
Date: Thu, 30 Jun 2016 09:25:04 +0200	[thread overview]
Message-ID: <1467271504-929-1-git-send-email-yegorslists@googlemail.com> (raw)

From: Yegor Yefremov <yegorslists@googlemail.com>

In most cases Python's package dependencies found in setup.py are
runtime dependencies and hence don't need to be mentioned in *.mk
file.

Also add '# runtime' tag to select statements in Config.in.

__create_mk_requirements() itself is left for future uses (cffi backend
handling etc.).

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 support/scripts/scanpypi | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/support/scripts/scanpypi b/support/scripts/scanpypi
index da578f4..f0d584a 100755
--- a/support/scripts/scanpypi
+++ b/support/scripts/scanpypi
@@ -466,8 +466,6 @@ class BuildrootPackage():
         lines += self.__create_mk_download_info()
         lines += self.__create_mk_setup()
         lines += self.__create_mk_license()
-        if self.pkg_req:
-            lines += self.__create_mk_requirements()
 
         lines.append('\n')
         lines.append('$(eval $(python-package))')
@@ -518,7 +516,7 @@ class BuildrootPackage():
         lines.append(bool_line)
         if self.pkg_req:
             for dep in self.pkg_req:
-                dep_line = '\tselect BR2_PACKAGE_{req}\n'.format(
+                dep_line = '\tselect BR2_PACKAGE_{req} # runtime\n'.format(
                     req=dep.upper().replace('-', '_'))
                 lines.append(dep_line)
 
-- 
2.1.4

             reply	other threads:[~2016-06-30  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30  7:25 yegorslists at googlemail.com [this message]
2016-06-30 22:04 ` [Buildroot] [PATCH] scanpypi: rework runtime dependency handling Thomas Petazzoni

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=1467271504-929-1-git-send-email-yegorslists@googlemail.com \
    --to=yegorslists@googlemail.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.