On 2023-02-20 02:06, Petr Pisar wrote:
I applaud the struggle for ensuring compatibility. However, I worry that it
will make downgrading RPM packages less feasible. Imagine a user who updates
a system, finds a regression in a library, attempts to downgrade the library
and it will result into downgrading later-built reverse dependencies only
because the library applied a (wrong) fix and the triplet has changed.
Do you know meaning of the numbers?
I will say that there are bits that I do not understand:
https://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html
https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
The documentation describes a system in which the library indicates the
first interface version it supported, and the latest interface version
it supports, as well as a revision counter that indicates changes in the
source that do not change the interface. As far as I can tell, this
manifests in a file name that ends in ".so.$(current -
age).$(age).$(revision)", which seems like a complicated way to arrive
at Semantic Versions. I don't know if "current" and "age" appear in the
ELF headers.
I'm sympathetic to the idea that providing the entire version number is
more strict than is necessary, but I'm not sure under what circumstances
it is safe to provide less. Are there cases where the version number is
more or less than three dot-separated number sequences? If we always
truncate to two, is that the correct thing to do for both versions with
only two numbers and for versions with more than three numbers?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
