On 10/12/2010 10:09 AM, Vadym Chepkov wrote:
> I disagree, users don't usually install libs directly, unless they intend to, 
> they would install corosync package if they need it.
> you can check yourself with majority of the packages: xen-libs don't require 
> xen, pacemaker-libs doesn't require pacemaker, net-snmp-libs doesn't require 
> net-snmp, just to name a few.
>
> Vadym
>

Vadym,

It is possible I am in error - packaging is not my strength.  Fabio, any 
comment on this topic?

Regards
-steve

> On Oct 12, 2010, at 11:32 AM, Steven Dake wrote:
>
>> On 10/12/2010 05:16 AM, Vadym Chepkov wrote:
>>> It was brought up in pacemaker mail list but this applies to corosync rpm 
>>> packaging as well.
>>> Libraries do not depend on "base" package, they are independent.
>>> This is how one can install several version of the same library (compat- 
>>> packages)
>>> Also it is possible to use corosync libraries without using corosync daemon 
>>> itself. (if one uses pacemaker with heartbeat, for instance).
>>>
>>>
>> Vadym,
>>
>> Its a general fedora policy that if a library depends in some way on the 
>> parent package, that the parent package is pulled into the system.
>>
>> The reason is for example:
>>
>> yum install corosynclibs
>>
>> If this only installed the libs, the user may think they were good to go, 
>> when in fact they also would need the corosync package.  The libs package 
>> would do nothing, except potentially satisfy some runtime dependency (the 
>> case you speak of).
>>
>> The tradeoff is the runtime dependency vs not confusing the user. Generally 
>> we go for principle of least surprise.
>>
>> Each distro is free to package however they like, however.  These spec files 
>> are only a guide of "best practices".
>>
>> Regards
>> -steve
>>
>>> --- corosync.spec.in        (revision 3058)
>>> +++ corosync.spec.in        (working copy)
>>> @@ -122,7 +122,6 @@
>>>   %package -n corosynclib
>>>   Summary: The Corosync Cluster Engine Libraries
>>>   Group: System Environment/Libraries
>>> -Requires: %{name} = %{version}-%{release}
>>>
>>>   %description -n corosynclib
>>>   This package contains corosync libraries.
>>>
>>> Vadym
>>> _______________________________________________
>>> Openais mailing list
>>> [email protected]
>>> https://lists.linux-foundation.org/mailman/listinfo/openais
>>
>

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to