From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11116] Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs
Date: Tue, 03 Jul 2018 22:24:03 +0000 [thread overview]
Message-ID: <bug-11116-163-rUxvPjfTlG@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11116-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11116
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
If I understand correctly, the problem is not that building a Python package
will write something to $HOME/.python-eggs (because as far as I can see, it
doesn't), but rather, that packages installed in $HOME/.python-eggs would
influence the build result when you run host-python, is that correct?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-07-03 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 18:36 [Buildroot] [Bug 11116] New: Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs bugzilla at busybox.net
2018-07-03 22:24 ` bugzilla at busybox.net [this message]
2018-09-07 19:25 ` [Buildroot] [Bug 11116] " bugzilla at busybox.net
2018-09-07 19:26 ` bugzilla at busybox.net
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=bug-11116-163-rUxvPjfTlG@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox