[Slackbuilds-users] tracking down SBo "dependencies"

[Andrzej Telszewski]

*From: *Jim <zsd+slackbuilds at jdvb.ca>
*To: *slackbuilds-users at slackbuilds.org
*Date: *29 Feb 2024 17:12:58
*Subject: *[Slackbuilds-users] tracking down SBo "dependencies"

> I recently upgraded the SBo dav1d, which upgraded the library from
> libdav1d.so.6 to libdav1d.so.7.
>
> Unfortunately, a couple of other SBo packages (libheif and vlc) had
> references to (specifically) libdav1d.so.6, which caused them to whine a
> bit.
>
> It was easy enough to recompile libheif and vlc after I found the problem,
> but this got me wondering...
>
> Does anyone have an easy way of tracking down this sort of "breakage" which
> might happen when upgrading an SBo package?
>
> Thanks.
>

Please consider tool like _slackrepo_.
It will rebuild a package in question should its dependiences be updated.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 691 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240229/5840e3aa/attachment.asc>