From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-setuptools: Add patch to prevent detecting the host installation
Date: Thu, 22 Aug 2013 08:12:01 -0300 [thread overview]
Message-ID: <5215F201.6090308@zacarias.com.ar> (raw)
In-Reply-To: <CAGm1_ksuhkORZYRNw1HPixOjBzRmk3MWgHp_yztMtHsYEyRrLw@mail.gmail.com>
On 08/22/2013 07:36 AM, Yegor Yefremov wrote:
I'll answer on the last mail to make it simpler, otherwise it would be a
lot of different mails :)
Basically there's two issues going on here.
First, Markos's patch is still necessary.
On a gentoo build host which is also a desktop and where setuptools
installed is "a common thing" thing fails no matter what is done without it.
Second, what Arnout said is valid too, but it's correctness rather than
a fix. python-netifaces doesn't need python-setuptools so that can be
dropped from DEPENDENCIES and Config.in, and PYTHONPATH in
HOST_PYTHON_SETUPTOOLS_INSTALL_CMDS is in fact redundant.
However if someone wants to concoct a patch for python-setuptools
there's an additional nag for the target variant - it should
depend/select BR2_PACKAGE_PYTHON_SSL since pypi forces https these days
otherwise it'll be a terrible experience.
Regards.
next prev parent reply other threads:[~2013-08-22 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:25 [Buildroot] [PATCH] python-setuptools: Add patch to prevent detecting the host installation Markos Chandras
2013-08-21 20:49 ` Arnout Vandecappelle
2013-08-22 8:19 ` Yegor Yefremov
2013-08-22 9:07 ` Yegor Yefremov
2013-08-22 9:17 ` Markos Chandras
2013-08-22 9:21 ` Arnout Vandecappelle
2013-08-22 9:18 ` Arnout Vandecappelle
2013-08-22 10:36 ` Yegor Yefremov
2013-08-22 11:12 ` Gustavo Zacarias [this message]
2013-08-22 11:17 ` Arnout Vandecappelle
2013-08-22 11:24 ` Gustavo Zacarias
2013-08-22 20:33 ` Markos Chandras
2013-08-22 20:37 ` Arnout Vandecappelle
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=5215F201.6090308@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.