Mailinglist Archive: opensuse-packaging (89 mails)

[Marcus Rueckert <darix@xxxxxx>]

On 2005-12-18 12:48:39 +0100, Pascal Bleser wrote:
> I'm getting productive with my new x86_64 box and noticed something... let's say "annoying" :)
> 
> I have quite some python module packages around and when they only include ".py" files (and not
> ".so" files), I mark them as BuildArch:noarch
> 
> Now I noticed while installing a python package (noarch) that it isn't found by python.
> 
> The reason: as it's noarch, it's being installed in /usr/lib/python2.4 (having built it on an x86
> box, and not an x86_64). But python only looks up its modules in /usr/lib64/python2.4
> 
> Does this mean that *all* python packages must be arch-specific, even when they're not (because they
> only include Python code and not native shared libs), just to have that path set correctly ?
> (that's a least what it looks like)

yes. i have the same problem with ruby. in ruby i could use /usr/lib all
the time but the FHS denies it for me. ruby does
/usr/lib/ruby/1.8/<somearch string> :)

for now ruby/python modules are always arch dependent.

darix