On 25/01/2025 05:42, Brian Inglis via Cygwin-apps wrote:
On 2025-01-24 20:31, Daisuke Fujimura via Cygwin-apps wrote:
I have decided that it is the mainstream practice in cygwin packages
to include information such as licenses in the runtime package, and I
have followed this practice.
However, I also believe that there is a possibility that these files
may conflict if the so version is incremented.
Example:
- https://cygwin.com/packages/x86_64/libchromaprint0/
libchromaprint0-1.2-1
- https://cygwin.com/packages/x86_64/libchromaprint1/
libchromaprint1-1.4.3-1
In your example, libchromaprint0 is no longer needed by anything:
Yeah, the package expiry logic should probably be more aggressive about
evicting in this case (it's only retained at the moment because
chromaprint doesn't exceed the global default package keep-count: of 3).
$ cygcheck-dep -cqSn libchromaprint{0,1}
libchromaprint0: is needed for ( )
libchromaprint1: is needed for ( gstreamer1.0-plugins-bad-free-extras
kid3-core libchromaprint-devel )
Multiple library ABI release documents do "conflict", but newer should
replace older, and licences are rarely changed because of multiple
If abi0 and abi1 runtime packages are installed at the same time,
there's no ordering guarantee provided by setup.
More generally, we shouldn't have file conflicts between packages
(although we don't have any mechanism to detect these, currently).
