What decides that a package is multilib?

[Mary Ellen Foster]

2009/6/29 Ondřej Vašík <ovasik at redhat.com>:
> Mary Ellen Foster píše v Po 29. 06. 2009 v 09:58 +0100:
>> Someone has just filed a bug that pl.i586 conflicts with pl.x86_64:
>>      https://bugzilla.redhat.com/show_bug.cgi?id=508515
>>
>> This is indeed true (I just verified it), but what I don't know is why
>> pl.i586 is in the multilib repository in the first place. How do
>> packages become multilib?
>
> You install files into libdir (%{_libdir}/%{name}-%{version}/*)- which
> differs for 32 and 64 bit architecture. Therefore is your package
> considered multilib.
>
> As binaries will probably always differ, the only and best way to
> resolve those multilib conflicts would be to have pl-libs subpackage.

Rats. Looks like I'll have to do a bit of fiddling, as upstream puts
everything (incliding binaries) into subdirectories of %{_libdir} and
then makes symbolic links into %{_bindir}. Oh well, can't be avoided I
guess ...

Thanks for the explanation!

MEF

-- 
Mary Ellen Foster  --  http://homepages.inf.ed.ac.uk/mef/
ICCS, School of Informatics, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.