Mailinglist Archive: opensuse-packaging (156 mails)

< Previous Next >
Re: [opensuse-packaging] Re: Extending Package Policy [was: A question about python naming]
  • From: dnh@xxxxxxxxxxxx
  • Date: Thu, 24 Jun 2010 11:55:22 +0200
  • Message-id: <20100624095522.GA4216@xxxxxxxxxxxxxxxxxx>

On Thu, 24 Jun 2010, Dave Plater wrote:
* %python_sitelib expands to /usr/lib/pythonX.Y/site-packages. This
is the install location for platform-independent modules.
* %python_sitearch expands to %{_libdir}/pythonX.Y/site-packages,
that is, either /usr/lib or /usr/lib64, depending on your architecture.
This is the install location for platform-dependent modules.

I'm not sure what a platform dependent python file is, this needs an
explanation. All scripts must be noarch, therefore a .py file would go
in %python_sitelib, which files would go into %python_sitearch?

Any .so or other binary(!), specifically compiled for a specific arch
should go into _sitearch, any non-arch-specific (which includes *.pyc
and AFAIK *.pyo, those are version specific, not arch specific) into

Just run
find $(rpm --eval '%python_sitelib') -name '*.so*'
find $(rpm --eval '%python_sitearch') -name '*.so*'

If all is well, the first command should output nothing, the latter
should output e.g.

You get the idea?


I refer to garlic as "the element without which life as we know it would be
impossible." Personally I believe that the garlic myth was started by vampires
as a way of enhancing the flavor of their food. -- Shmuel Metz
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups