default python spec template: python_sitelib vs python_sitearch

[Konstantin Ryabitsev]

On Mon, 2006-09-01 at 20:31 +0200, Ville Skyttä wrote:
> On Mon, 2006-01-09 at 12:46 -0500, Konstantin Ryabitsev wrote:
> 
> > Only .so files and friends should go to %{python_sitearch} -- so if you
> > have platform-independent files they should still go to
> > %{python_sitelib} even if you have other, platform-specific files.
> 
> I don't think I've every seen a package that would install things to
> both, but in contrast several others that dump either all into sitearch
> or all into sitelib.  A single arch dependent file seems to be enough
> for distutils for using arch specific dirs for all files installed in
> that batch.

Well, the purpose for sitearch is to be able to install multiple
architectures on the same machine. It will work fine if you put
everything into %{python_sitearch}, including platform-independent stuff
together with c-bindings, but that means you'll have duplicated files if
you install both .i386 and .x86-64. On the other hand, if you only put
c-bindings into %{python_sitearch}, and the platform-independent stuff
into %{python_sitelib}, the packages for both .i386 and .x86-64 won't
duplicate functionality and only one set of non-platform specific files
will be installed (granted that they are identical, of course, which
they should be).

Regards,
-- 
Konstantin Ryabitsev
McGill University WSG

River: "It's just an object. Doesn't mean what you think."