All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11116] New: Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs
Date: Wed, 27 Jun 2018 18:36:57 +0000	[thread overview]
Message-ID: <bug-11116-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11116

            Bug ID: 11116
           Summary: Buildroot should set PYTHON_EGG_CACHE instead of
                    writing files to ~/.python-eggs
           Product: buildroot
           Version: 2015.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: lotorev at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

There is PYTHON_EGG_CACHE variable for overriding directory for eggs files.

Buildroot should not use $HOME/.python-eggs directory and should set
PYTHON_EGG_CACHE internally to be independent on extra directories as less as
possible.

Existing packages in default $HOME/.python-eggs can influence on build
reproducibility.

Think of multiple Jenkins jobs building in parallel and using the same
$HOME/.python-eggs directory.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-06-27 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 18:36 bugzilla at busybox.net [this message]
2018-07-03 22:24 ` [Buildroot] [Bug 11116] Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs bugzilla at busybox.net
2018-09-07 19:25 ` 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@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 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.