On Wed, Oct 13, 2010 at 10:44 PM, Vadym Chepkov wrote:
>
> On Oct 12, 2010, at 6:14 PM, Vadym Chepkov wrote:
>
>>
>> On Oct 12, 2010, at 1:43 PM, Fabio M. Di NItto wrote:
>>
>>>
>>> what distribution are you looking at? In Fedora, where the spec file was
>>> first done as template for others to us
On Oct 12, 2010, at 6:14 PM, Vadym Chepkov wrote:
>
> On Oct 12, 2010, at 1:43 PM, Fabio M. Di NItto wrote:
>
>>
>> what distribution are you looking at? In Fedora, where the spec file was
>> first done as template for others to use and modify as needed, it's
>> pretty much mandatory to have
On 10/13/2010 1:17 PM, Vadym Chepkov wrote:
>
> On Oct 13, 2010, at 4:41 AM, Fabio M. Di Nitto wrote:
>>
>> I think the main difference is that some of those libraries are capable
>> of providing services without the daemon running. Something that´s not
>> true for all packages. Let´s put aside fo
On Oct 13, 2010, at 5:42 AM, Vladislav Bogdanov wrote:
>
> Just tested on dummy packages.
> yum decided to install cluster engine which has a "greater" name
> (although this can be a wrong assumption).
> I can attach rpm specs if you are interested in them (cleng1 and cleng2
> are identical "clus
On Oct 13, 2010, at 4:41 AM, Fabio M. Di Nitto wrote:
>
> I think the main difference is that some of those libraries are capable
> of providing services without the daemon running. Something that´s not
> true for all packages. Let´s put aside for a minute the build/linking
> case that used to be
On Oct 12, 2010, at 1:43 PM, Fabio M. Di NItto wrote:
> On 10/12/2010 07:09 PM, 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.
>
> This is pretty much Debian you are talking about.
>
>>
On 10/13/2010 11:42 AM, Vladislav Bogdanov wrote:
> 13.10.2010 11:41, Fabio M. Di Nitto wrote:
> ...
>>> It is absolutely legal to have both heartbeat and corosync packages
>>> installed even with that "Provides: cluster-engine" virtual dependencies
>>> as long as they do not have "Conflicts:" or "
13.10.2010 11:41, Fabio M. Di Nitto wrote:
...
>> It is absolutely legal to have both heartbeat and corosync packages
>> installed even with that "Provides: cluster-engine" virtual dependencies
>> as long as they do not have "Conflicts:" or "Obsoletes:" on each other
>> or some filesystem-level con
(purging some off topic bits ;))
On 10/13/2010 10:12 AM, Vladislav Bogdanov wrote:
>
>>> I already wrote that on pacemaker list, "-libs" is generally not a
>>> subpackage, but rather a "superpackage". If libraries are in base
>>> package then dependency of subpackages on base package is correct
>
13.10.2010 09:58, Fabio M. Di Nitto wrote:
...
>>> Pacemaker, is one of the few pieces of software that links against 2
>>> competitive "cores". It is cool enough to add support for both at the
>>> price of a few extra MB of harddisk used on the final system, with the
>>> benefit that everything
On 10/13/2010 6:52 AM, Vladislav Bogdanov wrote:
> 13.10.2010 07:14, Fabio M. Di NItto wrote:
>> On 10/13/2010 12:14 AM, Vadym Chepkov wrote:
>>
Also you might want to notice that there is no way any of the corosync
library can be of any use on a system without corosync main package.
>>>
11 matches
Mail list logo
