On 06/03/2024 15:39, Christian Franke via Cygwin-apps wrote:
Jon Turney wrote:
Thanks!
libafflib_CONTENTS="
usr/bin/cygafflib-*.dll
Any reason why this package doesn't include the soversion, i.e. why
not libafflib0?
Libtsk and libafflib are my first library packages, so I'm not sure what
the policy is. My recent package libtsk has been accepted without
soversion, so I omitted it also here. I assumed that the soversion will
I'm going to suggest that was an oversight in the review.
be added only when needed for new not backward compatible releases. The
upstream afflib project is mostly idling, so I don't expect any new
major lib versions in the near future.
If course, I could rename it to libafflib0 if desired.
As far as I know, there is no cost for doing this, and it saves grief if
upstream ever bumps the soversion.
Also, it's probably best to explicitly list the filename with soversion
in the CONTENTS, so that if upstream ever does change the soversion, it
will be detected as a packaging failure, rather than producing a package
with a mismatch between the soversion in it's name and in it's contents.
(Cygport should perhaps and detect and warn about apparently soversioned
libraries that aren't in appropriately named packages, but...)
