New comment by jirib on void-packages repository

https://github.com/void-linux/void-packages/pull/14061#issuecomment-528302061

Comment:
> > => 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](https://github.com/corosync/corosync/issues/501)

Solved, I'm preparing libknet1/libnozzle1 (new subpkg) fix which would support musl, https://github.com/void-linux/void-packages/pull/14215