On 14/06/19 20:13 +0200, Jan Pokorný wrote: > For the piece of mind, I am detailing the respective library that > would likely have been eligible for an explicit soname bump and why. > If you feel affected, please speak up so we have a clear incentive to > publish a "hotfix" for downstreams and direct consumers, otherwise > at least I don't feel compelled to anything immediate beyond this FYI, > and we shall rather do it in 2.0.3 even if not otherwise justified > with an inter-release delta, so there isn't a tiniest glitch possible > when 2.0.2 is skipped on the upgrade path (which is generally not > recommended but would be understandable if you happen to rely on > those very libpe_status.so ABI details).
Of course, an alternative applicable right now (also suitable for
those who self-compile ... and use libpe_status.so in their client
code at the same time) and avoiding the soname bump is to add the
original symbols back, e.g. using
__attribute__((alias ("original_name")))
for brevity.
> The mentioned ABI changes are:
>
> * libpe_status.so.28.0.2 (2.0.1: soname 28.0.1)
> - include/crm/pengine/remote.h: function renames, symbolic notation:
> { -> pe___}{is_baremetal_remote_node -> is_remote_node,
> is_container_remote_node -> is_guest_node,
> is_remote_node -> is_guest_or_remote_node,
> is_rsc_baremetal_remote_node -> resource_is_remote_conn,
> rsc_contains_remote_node -> resource_contains_guest_node}
>
> (all other ABI breaking changes appear self-contained for not
> being related to anything exposed through what could be considered
> a public header/API -- not to be confused with ABI)
--
Jan (Poki)
pgpBiHNh8gfAK.pgp
Description: PGP signature
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/
