Arch Linux

Not really understanding what the story here is BTW, since the PKGBUILD runs two different makefiles, the first of which builds a test suite that is never utilized in a check() function.

And instead of using the `make install` target I guess because it also installs the testsuite if built, this package is relying on the fact that install(1) will copy the target of a symlink, rather than copying the symlink itself, to install the libcryptopp.so symlink into "$pkgdir". Which only works by accident. ;)

(It would be trivial to rm -rf "$pkgdir"/usr/{bin,share}/ after using the proper `make install` target, for what it's worth. And this is a lot more indicative of what is going on, besides being forwards-compatible with upstream changes to the install process...)

Also why isn't this pkg-config file upstreamed...

I have a local fix, however pacman now complains when upgrading:

(1/1) checking keys in keyring [--------------------------------------------------------] 100%
(1/1) checking package integrity [--------------------------------------------------------] 100%
(1/1) loading package files [--------------------------------------------------------] 100%
(1/1) checking for file conflicts [--------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
crypto++: /usr/lib/libcryptopp.so.5.6 exists in filesystem
Errors occurred, no packages were upgraded.

I tried to remove the symlink in a pre_upgrade() install script, but it didn't work (probably the script runs after checking for file conflicts).

Unless somebody comes up with a solution I guess it will require a news on the website.

Yes, this requires a manual intervention.

Yes, conflicts are checked before the package is extracted and has its pre_upgrade scripts run etc. so users will have to do manual intervention unless by coincidence the soname were changing at the same time.

(Something similar has happened once or twice with python and compiled bytecode, but that rarely causes problems except when running python software as root.)

crypto++ 6.0 has been released, so I will use the opportunity of the upgrade to fix this bug.

(and thankfully, upstream now provides an autotools build system in addition to the hand-crafted Makefiles...)

Fixed in crypto++ 6.0.0-2 (currently in [community-staging] for rebuilds)