On Sat, 31 May 2025, Brian Inglis via Cygwin-apps wrote: > > Note that the previous releases are 0.23.4-2 libgit2_23, 0.24.6-1 libgit2_24, > 0.25.1-1 libgit2_25, unfortunately, so 1.9.0-1 would have to be libgit2_109 > for rpmvercmp to sort it higher, with appropriate changes elsewhere!
Does this matter? To me, this is the package *name* not package *version* so rpmvercmp shouldn't come into play, should it? Or am I missing something? > Also note that libgit2-glib1.0 provides a wrapper for a newer libgit2 release: > > 0.26.2-1 libgit2-glib1.0-devel > 0.26.2-1 libgit2-glib1.0-doc > 0.26.2-1 libgit2-glib1.0_0 That's the beauty of soversioned package names, that one can put out a new version of libgit2 as a new package (libgit2_1.9) without having to find & rebuild or update other packages that might depend on an older version?
