[Slackbuilds-users] tracking down SBo "dependencies"

[Arnaud]

> > However, tracking potential breakages could be done using hoorex.
> 
> Not in this case...
> 
> > # hoorex -i dav1d This'll list all installed packages requiring directly
> > dav1d.
> 
> And there's the problem... Neither vlc nor libheif (nor maybe others I
> haven't found yet) *directly* require dav1d, so hoorex doesn't list them.

So I've looked again, and sbbdep is quite useful.
So my libheif is built with dav1d, but not my VLC.
And then :
$ hoorex -i dav1d
dav1d libheif
$ sbbdep --whoneeds /var/log/packages/dav1d-1.4.0-x86_64-1yth
dav1d-1.4.0-x86_64-1yth
libheif-1.17.6-x86_64-1yth

Which returns what is relevant.
Then I rebuilt VLC, which might probably have been built without dav1d.
And then :
$ sbbdep --whoneeds /var/log/packages/dav1d-1.4.0-x86_64-1yth
dav1d-1.4.0-x86_64-1yth
libheif-1.17.6-x86_64-1yth
vlc-3.0.20-x86_64-1yth

So it does work, for binary dependencies.
I know that either libheif or vlc could require rebuilding after an update of
dav1d.

To be noted :
I haven't tested building vlc with libdav1d.so.6, then updating dav1d to
libdav1d.so.7, and asking sbbdep.
It might fail, because the link is broken, vlc wouldn't show a link to dav1d
since it doesn't link to libdav1d.so.7

But, you could update sbbdep database before an update, and ask without updating
the sbbdep database.

Let's say, it might not be perfect, and may require something on top of it, to
detect, through comparison of dependencies before and after an update, what
links may have been severed.
As I said, I didn't test such a situation.


For perl and python (and haskell, and... maybe other), it's less problematic,
since most dependencies are SBo-related, hence we have a dependency tree
available. That would be more True on stable 15.0 where python/perl and system
modules aren't very updated, but could be pretty wrong on -current.

 - Yth.