From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-setuptools: Add patch to prevent detecting the host installation
Date: Thu, 22 Aug 2013 13:17:10 +0200 [thread overview]
Message-ID: <5215F336.8050106@mind.be> (raw)
In-Reply-To: <5215F201.6090308@zacarias.com.ar>
On 22/08/13 13:12, Gustavo Zacarias wrote:
> 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.
Markos's patch, or a yet-to-be-created patch that adds $(TARGET_DIR) to
the PYTHONPATH instead of passing the system's pythonpath?
> 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.
Actually I didn't realize the PYTHONPATH setting for the host variant
was redundant :-) I was only talking about the target.
> 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.
But I guess that is a separate patch.
Anyway I'm not sure if the target variant is that relevant, because it
will not be able to install anything that requires compilation...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-08-22 11:17 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
2013-08-22 11:17 ` Arnout Vandecappelle [this message]
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=5215F336.8050106@mind.be \
--to=arnout@mind.be \
--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.