[WIP] New package: corosync-3.0.2

[jirib]

The Corosync Cluster Engine is a Group Communication System with additional features for implementing high availability within applications.

Needed for future pacemaker package.

[jirib]

Any idea about following issue?

$ xbps-query -l | grep corosynclib
ii corosynclib-3.0.2_1                     Corosync libraries
$ sudo xbps-install --repository=hostdir/binpkgs/corosync/ corosynclib-devel
MISSING: corosynclib=>3.0.2_1
Transaction aborted due to unresolved dependencies.

[Hoshpak]

=> looks odd, I think it should be >=. However you should not need to add that manually since dependencies on shard libraries are automatically detected by xbps-src while building the package. Following the usual pattern for libraries, the sub-package should be called `libcorosync'. Haven't reviewed the rest of the template yet.

[jirib]

=> looks odd, I think it should be >=. However you should not need to add that manually since dependencies on shard libraries are automatically detected by xbps-src while building the package. Following the usual pattern for libraries, the sub-package should be called `libcorosync'. Haven't reviewed the rest of the template yet.

Thanks, it was this typo.

BTW, as libknet1 does not build on musl archs, how should this package be treated? Should I define it to be only for non-musl archs? IIUC corosync can't be easily told to be build without 'knet' transport now, see corosync/corosync#501

[jirib]

=> looks odd, I think it should be >=. However you should not need to add that manually since dependencies on shard libraries are automatically detected by xbps-src while building the package. Following the usual pattern for libraries, the sub-package should be called `libcorosync'. Haven't reviewed the rest of the template yet.

Thanks, it was this typo.

BTW, as libknet1 does not build on musl archs, how should this package be treated? Should I define it to be only for non-musl archs? IIUC corosync can't be easily told to be build without 'knet' transport now, see corosync/corosync#501

Solved, I'm preparing libknet1/libnozzle1 (new subpkg) fix which would support musl, #14215