On Wed, 17 Mar 2021, Efraim Flashner wrote: > On Tue, Mar 16, 2021 at 01:49:51PM +0100, Léo Le Bouter via Guix-patches via wrote: >> On Tue, 2021-03-16 at 22:47 +1100, Ben Sturmfels via Guix-patches via >> wrote: >> > Thanks, that solves my problem. One follow-up question - is it better >> > to >> > use the ".so" link or the specific "so.0"? >> >> Use the more specific one since that is a symlink for a fixed ABI, if >> the main library changes ABI it can then symlink with a bumped number >> to indicate that and not break any dependent package. If you use the >> less specific .so file directly then your package may suffer an ABI >> break. > > The package gets rebuilt each time so it is less likely with Guix. > However, if you substitute libsndfile.so and the full text is > libsndfile.so.0.0.23 (or something similar) then you'll still end up > with /gnu/store/...libsndfile.../libsndfile.so.0.0.23. Thanks Efraim, Léo and Nicolò for the info on .so links. This patch is now waiting on updates to libsndfile in core-updates. I'll post an updated patch when that's merged. For now, I've inlined this into MediaGoblin's guix-env.scm so I can keep working on the packaging there. Regards, Ben