Resolution of the library-path mess

[Daniele Nicolodi]

On 10/6/17 4:21 PM, Gary E. Miller wrote:
> Yo Daniele!
> 
> On Fri, 6 Oct 2017 15:59:05 -0600
> Daniele Nicolodi <daniele at grinta.net> wrote:
> 
>> On 10/6/17 1:46 PM, Gary E. Miller via devel wrote:
>>> Yo Daniele!
>>>
>>> On Thu, 5 Oct 2017 23:39:51 -0600
>>> Daniele Nicolodi via devel <devel at ntpsec.org> wrote:
>>>   
>>>> The reason why Python does not
>>>> include /usr/local folders in his search path by default is: what
>>>> if you want to install an alternative Pythion _interpreter_
>>>> there?   
>>>
>>> Uh, no.  Each interpreter makes it's own path under /usr/local
>>>
>>> Easy to see:
>>>
>>> $ ls /usr/local/lib/py* -ld
>>> drwxr-xr-x 2 root root 4096 Nov  4  2016 /usr/local/lib/pylib
>>> drwxr-xr-x 3 root root 4096 Jan 23  2017 /usr/local/lib/python2.7
>>> drwxr-xr-x 3 root root 4096 Nov 21  2016 /usr/local/lib/python3.4  
>>
>> Is this serious?  Are you confusing different interpreters with
>> interpreter minor version?
> 
> Nothing to confuse. Clearly separate.
> 
>> What if I want to have 2.7.1 and 2.7.2, for example?
> 
> Gentoo can easily do that as well.  Pretty common on gentoo.

How? It is clearly not possible with the scheme you described before.

It is not clear to me how an user component installing files in /usr is
seen as a violation of policy, but a system component installing or
picking up files into /urs/local is fine.

Cheers,
Daniele