<div dir="auto"><div>This would only show dependencies of dav1d. It wouldn't show any packages that depend on dav1d (unless there was a circular dependency), so it wouldn't help find things that would be broken.</div><div dir="auto"><br></div><div dir="auto">You could grep all the queue files for dav1d, but that would only show the packages that had it as a hard dependency. Several will add support if dav1d is found on the system (like VLC) without needing to specify it on the REQUIRES line in the .info.</div><div dir="auto"><br></div><div dir="auto">It's certainly one benefit of building in a clean system to prevent picking accidental dependencies (which slackrepo does very well when set up properly).</div><div dir="auto"><br></div><div dir="auto">Jeremy<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Sat, Mar 2, 2024, 1:59 AM Jheengut Pritvi <<a href="mailto:z.coldplayer@gmail.com">z.coldplayer@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">sqg -p dav1d</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 29 Feb 2024 at 20:12, Jim <<a href="mailto:zsd%2Bslackbuilds@jdvb.ca" target="_blank" rel="noreferrer">zsd+slackbuilds@jdvb.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I recently upgraded the SBo dav1d, which upgraded the library from<br>
libdav1d.so.6 to libdav1d.so.7.<br>
<br>
Unfortunately, a couple of other SBo packages (libheif and vlc) had<br>
references to (specifically) libdav1d.so.6, which caused them to whine a<br>
bit.<br>
<br>
It was easy enough to recompile libheif and vlc after I found the problem,<br>
but this got me wondering...<br>
<br>
Does anyone have an easy way of tracking down this sort of "breakage" which<br>
might happen when upgrading an SBo package?<br>
<br>
Thanks.<br>
Jim<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div></div></div>