Mailinglist Archive: opensuse-packaging (89 mails)

[Pascal Bleser <pascal.bleser@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

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)

cheers
- --
  -o) Pascal Bleser     http://linux01.gwdg.de/~pbleser/
  /\\ <pascal.bleser@xxxxxxxxx>       <guru@xxxxxxxxxxx>
 _\_v The more things change, the more they stay insane.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDpUyXr3NMWliFcXcRAp1BAJ9DtArUzz7Gf6k0Esr0DZrTzOhFwACfVAew
8ScMB+ffubF7IVVfwfyCQCQ=
=RKkv
-----END PGP SIGNATURE-----