> imposes its own signal handling on users when the db is open
Can turn that off since 56f49d7f5af7c1c8a3eb478431356195adbfdd25 right?
> and our ABI hasn't been particularly stable historically
Maintaining C shared libraries is indeed extremely hard. I've messed up in the
past and only just barely caught it before releases etc. That said there are
nice tools now like [libabigail](https://pagure.io/libabigail) - should be easy
to set that up on CI here right?
(I still need to do that for ostree)
> dbus library itself is much more stable AIUI.
Yeah, libdbus as a C shared library has been fine and will continue to be so,
but exposing an API over DBus is a separate thing with long term commitments.
If we're effectively saying most projects shouldn't be using librpm to read the
rpm database effectively (that seems like what you're implying) that's a rather
radical thing right? Maybe I am misunderstanding though.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1255#issuecomment-649535595
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
