All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-coherence: select pyasn1 instead of pyasn
Date: Mon, 13 Apr 2020 17:17:04 -0600	[thread overview]
Message-ID: <20200413231704.124258-1-james.hilliard1@gmail.com> (raw)

The python-pyasn package is an outdated version of python-pyasn1 and
should not be used.

We no longer need to depend on BR2_INSTALL_LIBSTDCPP as python-pyasn1
does not depend on it.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 package/python-coherence/Config.in | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/package/python-coherence/Config.in b/package/python-coherence/Config.in
index 63427964a7..0f50080e67 100644
--- a/package/python-coherence/Config.in
+++ b/package/python-coherence/Config.in
@@ -1,15 +1,10 @@
 config BR2_PACKAGE_PYTHON_COHERENCE
 	bool "python-coherence"
 	depends on BR2_PACKAGE_PYTHON
-	depends on BR2_INSTALL_LIBSTDCPP # python-pyasn
 	select BR2_PACKAGE_PYTHON_TWISTED
 	select BR2_PACKAGE_PYTHON_ZOPE_INTERFACE
-	select BR2_PACKAGE_PYTHON_PYASN
+	select BR2_PACKAGE_PYTHON_PYASN1
 	help
 	  A DLNA/UPnP Media Server and Framework for the Digital Living.
 
 	  https://github.com/coherence-project/Coherence
-
-comment "python-coherence needs a toolchain w/ C++"
-	depends on BR2_PACKAGE_PYTHON
-	depends on !BR2_INSTALL_LIBSTDCPP
-- 
2.20.1

             reply	other threads:[~2020-04-13 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 23:17 James Hilliard [this message]
2020-04-19  8:18 ` [Buildroot] [PATCH 1/1] package/python-coherence: select pyasn1 instead of pyasn Thomas Petazzoni
2020-04-19  8:21   ` James Hilliard
2020-04-19  8:24     ` 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=20200413231704.124258-1-james.hilliard1@gmail.com \
    --to=james.hilliard1@gmail.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.