Le jeudi 23 novembre 2006 à 14:26 +0100, Loïc Minier a écrit :
> > This is already the case. I believe it has been added when we discovered
> > problems due to *.so and *.py being in different directories.
> > You might want to close this bug.
> 
>  I still think there's currently no protection against silent breakage
>  in python-support.  Packages are still ./configured to install python
>  modules into /usr/lib, but this does not reflect the runtime location
>  of files.  This is particularly a problem for plugins mechanisms.

Only for plugins that aren't relocatable. This can be worked around in
the ./configure, but a better solution is to avoid such mechanisms.

>  I suppose it would be enough to 1) document the problem in the
>  python-support documentation 2) recommend people to ./configure with a
>  python path of /var/lib/python-support/pythonX.Y 3) stop moving files
>  from /usr/lib/pythonX.Y into /var/lib/python-support.  3) is obviously
>  for the long term.

The real long term solution is to have python look for byte-compiled
files directly in /var/cache/python/$hash, just like fontconfig does.
Having done things right from the beginning would have saved a lot of
trouble.
-- 
Josselin Mouette                /\./\

"Do you have any more insane proposals for me?"


Reply via email to