[Slackbuilds-users] tracking down SBo "dependencies"
Jim
zsd+slackbuilds at jdvb.ca
Thu Feb 29 19:46:27 UTC 2024
On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote:
> *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?
> Please consider tool like _slackrepo_.
> It will rebuild a package in question should its dependiences be updated.
Hi Andrzej,
thanks for that pointer.
>From other discussions it's not clear that slackrepo would catch this, but
maybe I'll find out.
Jim
More information about the SlackBuilds-users
mailing list