The build procedure for EVMS will compile all plugins by default, provided the system has support for the plugin, with one exception... the "ha" and "hb2" plugins are mutually exclusive: they cannot both be built (the default being only the "ha" plugin). The current ebuild for EVMS provides no way to select the "hb2" plugin instead of "ha". Could this choice be provided as a USE flag? Ie, which sets the "--disable-ha" configure option if hb2 is desired? Reproducible: Always Steps to Reproduce: 1.emerge heartbeat 2.emerge evms Actual Results: no hb2 plugin present in /lib/evms/*/ This is the relevant part of the configure output when emergeing EVMS: ... configure: checking which EVMS plugins to build: configure: building bbr configure: building bsd configure: building bbr_seg configure: building csm configure: building disk configure: building dos configure: building drivelink configure: building error configure: building ext2 configure: building fat configure: building gpt configure: building ha configure: not building hb2 ... cannot build both ha and hb2 configure: building jfs configure: building lvm configure: building lvm2 configure: building mac configure: building md configure: building multipath configure: building ntfs configure: building ocfs2 configure: building ogfs configure: building reiser configure: building replace configure: not building rsct ... requires glib library configure: not building s390 ... requires asm/vtoc.h configure: building snapshot configure: building swap configure: building xfs configure: checking which EVMS user interfaces to build: ...
Created attachment 126914 [details, diff] evms-2.5.5-r6-hb2.patch Patch against evms-2.5.5-r6 adding a hb2 keyword. Why on earth they decided to name one module ha and one hb2 I don't know, but anyhoo.
Fixed in CVS. I added the USE flags hb and hb2 to be able to disable the support for heartbeat-1/-2 even if it's installed. Added the correct dependencies for both of them...
