it is hard for optional dependencies. for hard deps, you can do an
advanced reverse dependency(full) search on slackbuilds.org
Personally I keep build lists for the things I use, including optional
deps, and build flags and other special build instructions.
It is more work, and when a package is updated one should recheck the
deps incase they have changed, but it helps, so I rebuild
all packages that directly depend on the updated one. Occasionally you
have to rebuild further up the dep tree, but it works
most of the time.
Regards, Tim
On 29/02/2024 16:12, Jim wrote:
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.
Jim
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
