[ClusterLabs] Antw: Pacemaker API structure and pkg-config files

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Mon Jan 14 10:50:49 EST 2019

>>> <wferi at niif.hu> schrieb am 14.01.2019 um 11:48 in Nachricht
<87va2rjyzv.fsf at lant.ki.iif.hu>:
> Hi,
> Recently I spent some time mapping the interrelations of the C header
> files constituting the Pacemaker API.  In the end I decided they were so
> tightly interdependent that there was really no useful way to ship parts
> of the API separately, thus I did away with the separate lib*‑dev Debian
> packages and merged them into a single pacemaker‑dev package, much like
> the pacemaker‑libs‑devel RPM package created by the upstream spec file.

Time to use the machete in the source code! ;-)

> Now I'm looking at DLM, which uses the fencing API, and trying to use
> pkg‑config for supplying the necessary flags.  I got pretty sure the
> pkg‑config files are incorrect, for example neither declares the
> libxml‑2.0 dependency in stonith‑ng.h (which is to be dropped, but still
> there).
> I'd like to get the pkg‑config support of Pacemaker corrected, but
> before I start cooking up patches, I need to get an idea of the
> preferred direction upstream.  For a start: is providing multiple
> pkg‑config files (still) reasonable?
> ‑‑ 
> Thanks,
> Feri
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> https://lists.clusterlabs.org/mailman/listinfo/users 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org 

More information about the Users mailing list