Es schrieb Guillaume Rousse:
>
> Ainsi parlait Pixel :
> > Guillaume Rousse <[EMAIL PROTECTED]> writes:
> > > Why does rpmlint complains when it finds .so libs in non-devel package ?
> > > Most of the time, it's a simple link to a versioned file (*.so.*) of the
> > > same package. So why put them in another one ?
> >
> > otherwise you'll get conflicts when installing 2 libs packages.
> You mean you can have 2 libs package, but not 2 devel packages simultaneously
Right, what would it be good for, to have two devel packages for the same
lib (diffrent versions)?
Let's supose the devel package comes with "foo.h". Some functions have now
a diffrernt syntax in "libfoo.so.3" compared to "libfoo.so.2". RPM is only
able to have one version of "/usr/include/foo.h" (lets say the one from
libfoo 2). If you now try to install libfoo 3 rpm you get a conflict error
and RPM stops the installation ... => you can have diffrent versions of
libfoo installed (with some applications build against "libfoo.so.2" and
some against "libfoo.so.3") but only one devel package ...
--
��������������������������������������������������������_�����
Tsch�ss�und�bis�demn�chst/�bient�t,������������������_|_|_���
�������������������������������������������������������(")���*
������������������������������������Stefan�������������/v\ �/�
������������������������������������������������������(���)���Penguin�Powered!
�+----------------------------------------------------(m-m)------------------+
�|�Stefan�Siegel���������������������|�http://www.student.uni-kl.de/~siegel/ |
�|�Kurt-Schumacher-Str.�34�/�App.144�|�mailto:[EMAIL PROTECTED] ���|
�|�D-67663 Kaiserslautern������������|�PGP�Public�Key:�����������������������|
�|�Tel.:�+49-631-18269���������������|���finger�-l�[EMAIL PROTECTED] ��|
�+---------------------------------------------------------------------------+
