From: Jean Delvare <jdelvare@suse.de>
To: "Ondřej Lysoněk" <olysonek@redhat.com>
Cc: linux-hwmon@vger.kernel.org
Subject: libsensors soname bump
Date: Sun, 16 Dec 2018 12:43:44 +0100 [thread overview]
Message-ID: <20181216124344.49d06b69@endymion> (raw)
Hi Ondřej,
You have recently released lm-sensors 3.5.0 with a new soname for
libsensors:
-LIBMAINVER := 4
-LIBMINORVER := 4.0
+LIBMAINVER := 5
+LIBMINORVER := 0.0
-#define SENSORS_API_VERSION 0x440
+#define SENSORS_API_VERSION 0x500
This is declaring the new library as incompatible with the previous
version, meaning that distributions will have to build and ship both
libsensors4 and libsensors5 for a long time until all applications have
been updated and rebuilt to link with the new library. This is a
significant effort for the whole community and should only be done when
necessary.
In this specific case, I can't see what warranted such a change of
major library version change. From
lm-sensors/doc/developers/release_checklist:
Remember: update main number when interface changes, minor if new
functionality is added, and patch if only bugs are fixed.
In this case I can only see new functionality added, there is no
interface change. Therefore the correct value for SENSORS_API_VERSION
was 0x450, not 0x500. This would avoid the parallel maintenance and
installation of 2 versions of the library for several years to come.
Would you consider quickly releasing lm-sensors 3.5.1 with the proper
library version number, to save all that work to all application
authors/maintainers and distribution package maintainers?
Thanks,
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2018-12-16 11:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 11:43 Jean Delvare [this message]
2018-12-17 9:46 ` libsensors soname bump Ondřej Lysoněk
2018-12-17 10:35 ` Ondřej Lysoněk
2018-12-17 10:59 ` Jean Delvare
2018-12-17 11:27 ` Aurelien Jarno
2018-12-17 11:48 ` Ondřej Lysoněk
2018-12-17 12:06 ` Ondřej Lysoněk
2018-12-17 12:06 ` Ondřej Lysoněk
2018-12-17 10:48 ` Jean Delvare
2018-12-18 17:06 ` Ondřej Lysoněk
2018-12-18 17:06 ` Ondřej Lysoněk
2018-12-19 15:10 ` Jean Delvare
2018-12-19 15:10 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181216124344.49d06b69@endymion \
--to=jdelvare@suse.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=olysonek@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.