On Tue, Jan 24, 2006 at 09:30:43PM +0200, Elan Ruusamäe wrote:
> after some discussion with twittner,
> 
> > > $ python -c 'import sys; print sys.path'
> default paths:
> > > ['', '/usr/lib64/python24.zip', '/usr/share/python2.4',
> > > '/usr/share/python2.4/plat-linux2', \
> > > '/usr/share/python2.4/lib-tk', '/usr/lib64/python2.4/lib-dynload', \
> paths defined from site.py[co]:
> > > '/usr/lib/python2.4/site-packages', '/usr/share/python2.4/site-packages']
> 
> so, my problem was that i had installed both athlon and amd64 packages on 
> system (due wanting to run 32-bit openoffice, which needs python-libs)
> 
> $ q -qf  /usr/share/python2.4/site.py[co]
> python-libs-2.4.2-3.amd64
> python-libs-2.4.2-3.athlon
> python-libs-2.4.2-3.amd64
> python-libs-2.4.2-3.athlon
> 
> accroding to search path, moving /usr/share/python2.4/site.py[co] to 
> for amd64 package: /usr/lib64/python2.4/lib-dynload/
> for athlon package: /usr/lib/python2.4/lib-dynload/
> solved my problem.
> 
> so there are several problems
> 1. site.py[co] is in arch independant location, but contains hardcoded path 
> to 
> arch dependant location

Yes, it's known problem and already discussed[1], but no solution has been
implemented so far.

[1] in Polish language, but example patches should be readable in any
language

http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2004-December/121358.html
http://lists.pld-linux.org/mailman/pipermail/pld-devel-pl/2004-December/121361.html

[...]
> if taking look on other distros, then the just put all their files to 
> /usr/lib 
> or /usr/lib64
> - http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/SPECS/python/
> - http://cvs.fedora.redhat.com/viewcvs/rpms/python/FC-4/

Some time ago we moved arch-independent stuff (and, unfortunately,
distutils) to /usr/share to allow creating packages with python bytecode
as noarch.


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Reply via email to