[Slackbuilds-users] tracking down SBo "dependencies"
Petar Petrov
slackalaxy at gmail.com
Fri Mar 1 10:32:10 UTC 2024
what about them? Of course it won't 'catch' these. Still, checking the
*.so libs is a great help.
do you think that since it won't work for perl, python and ruby such
tool is unneeded?
-p
On Fri, 1 Mar 2024 at 12:28, Didier Spaier <didier at slint.fr> wrote:
>
> What about the non-binary deps (perl, python and ruby...)?
>
> Cheers,
> Didier
>
> Le 01/03/2024 à 11:19, Petar Petrov a écrit :
> > revdep checks for broken *.so, so it would not matter whether your
> > deps were optional or not. People running -current, who install stuff
> > from SBo, would greatly benefit from such a tool.
> >
> > regards,
> >
> > -p
> >
> >
> > On Fri, 1 Mar 2024 at 12:16, Tim Dickson via SlackBuilds-users
> > <slackbuilds-users at slackbuilds.org> wrote:
> >>
> >> the problem is the optional dependencies. how does a tool know which
> >> options you like.
> >> Only when such a tool which has your preferred optional deps recorded
> >> exists, can there
> >> be a way to reverse dep without missing out bits.
> >> regards, Tim
> >>
> >> On 01/03/2024 09:38, Petar Petrov wrote:
> >>> there were several discussions about Slackware needing a tool such as
> >>> revdep, to check for issues like this. Search LQ, however, I did not
> >>> find a good solution that just works. I got advice to make my own
> >>> tool, as well as, statements how people use their own "home made"
> >>> tools for this.
> >>>
> >>> -p
> >>>
> >>> On Thu, 29 Feb 2024 at 18:12, Jim <zsd+slackbuilds at jdvb.ca> 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
More information about the SlackBuilds-users
mailing list