On Sun, 22 Nov 2015, Jacek Konieczny wrote:
> Hi,
>
> Most Python HOWTOs and similar resources suggest using 'pip',
> 'easy_install' or other tools to install python modules or python-based
> programs. The problem is, that in PLD those tools would install modules
> in /usr/{lib{64},share}/pythonX.Y/site-packages – the same place, where
> python modules from our RPM packages go.
>
> This is a mess and may destroy already installed packages – using pip to
> install a single innocent program may cause chain reaction of installing
> dependency modules and overwitting old versions of those already in the
> system.
>
> virtualenv can help, but only if one chooses to use it.
>
> I suggest patching python, python3 and, if neccessary, other packages,
> so distutils/setuptools/pip would install Python modules to /usr/local
> by default – like autoconf configure scripts do. Python would look for
> modues in /usr/local first and then in /usr.
Makes sense. Go ahead and do it.
--
Jan Rękorajski | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
