On 2025-05-31 19:40, Jeremy Drake via Cygwin-apps wrote:
On Sat, 31 May 2025, Jon Turney wrote:
On 26/05/2025 19:41, Jeremy Drake via Cygwin-apps wrote:
On Sun, 25 May 2025, Jon Turney wrote:
Should I add a big comment documenting the test failures, or a separate
file?
No wrong answers.
I guess I'd go for a separate file, but I don't mind.
PKG_NAMES="git2 libgit2_1_9 libgit2-devel"
Sorry for not spotting this earlier, but I think the conventional name here is
"libgit2_1.9" (i.e. the underscore just separates the upstream name (when it
happens to end in digits) from a trailing soversion number, it doesn't replace
all the dots in it.
OK, wasn't sure, as soon as I saw that I was going to try to make a
variable name with a dot in it, I went with the underscore. But it seems
I just stick with the underscore in the variable names.
If we're going to package the 'git2' tool, maybe it should have a description
which makes it clearer what it's use is (debugging libgit2, not working with
git repor?)
I wouldn't be opposed to either not package it, or stick it in
libgit2-devel. I don't really know what it's used for tbh.
If git2 is a developer tool used with libgit2, then libgit2-devel would be a
better place for it, with libgit2_.. as the binary package.
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!
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
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
