[Buildroot] [Bug 11116] New: Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs

[Buildroot] [Bug 11116] New: Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs

[bugzilla at busybox.net]

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.

[Buildroot] [Bug 11116] Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs

[bugzilla at 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.

[Buildroot] [Bug 11116] Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs

[bugzilla at busybox.net]

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

Vitaliy Lotorev <lotorev@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #2 from Vitaliy Lotorev <lotorev@gmail.com> ---
> 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),

It does on my side, it appears I was using custom python-serial package that
used distutils instead of setuptools (which is used in recent Buildroot
versions). After switching to stock Buildroot package no writing is done to
$HOME/.python-egss directory anymore.

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

[Buildroot] [Bug 11116] Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs

[bugzilla at busybox.net]

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

Vitaliy Lotorev <lotorev@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

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