Bug 11116

Summary:	Buildroot should set PYTHON_EGG_CACHE instead of writing files to ~/.python-eggs
Product:	buildroot	Reporter:	Vitaliy Lotorev <lotorev>
Component:	Other	Assignee:	unassigned
Status:	CLOSED INVALID
Severity:	normal	CC:	buildroot, lotorev
Priority:	P5
Version:	2015.08
Target Milestone:	---
Hardware:	All
OS:	Linux
Host:		Target:
Build:

Description Vitaliy Lotorev 2018-06-27 18:36:57 UTC

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.

Comment 1 Arnout Vandecappelle 2018-07-03 22:24:03 UTC

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?

Comment 2 Vitaliy Lotorev 2018-09-07 19:25:13 UTC

> 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.