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. > > Of cause there is. What if you just compile pacemaker, for instance? > Why would you need to install corosync daemon to just link pacemaker binary? >
So you are telling me that your build machine doesn't have a few MB of harddisk to install corosync rpm? If that's the problem you are trying to solve, I think you have some other issues to solve first, because in that condition, you will likely be unable to apply any security updates to any of the other packages. and as I explained in another email in this thread, we do have the exact same issue for users of pacemaker with corosync that finds themselves installing heartbeat. The major difference is that we do acknowledge the reason why is done that way and live with it. Life goes on. 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 users might want, works out of the box. So let's assume both heartbeat and corosync drops that Require lines, I am willing to bet in a matter of a week or two, somebody is going to report that installing pacemaker doesn't install required dependencies on corosync or heartbeat. Fabio _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
