[Slackbuilds-users] spring cleaning some packages

2024-02-29 Thread Ruben Schuller
Hi list, I don't really use these anymore, so if anyone wants them feel free - I think they could be in better hands :) libtermkey libvterm lua-lpeg lua-luv lua-mpack unibilium vis nim Most of these are dependencies for neovim and vis - except nim. I will try to maintain them if no one wants

Re: [Slackbuilds-users] spring cleaning some packages

2024-02-29 Thread Alexander Verbovetsky
Hello, On Thu, Feb 29, 2024 at 12:39:51PM +0100, Ruben Schuller wrote: > I don't really use these anymore, so if anyone wants them feel free - > I think they could be in better hands :) > > libtermkey > libvterm > lua-lpeg > lua-luv > lua-mpack > unibilium > vis > nim > > Most of these are

[Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jim
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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Andrzej Telszewski
*From: *Jim *To: *slackbuilds-users@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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Erich Ritz via SlackBuilds-users
On Thursday, February 29th, 2024 at 10:12 AM, 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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Arnaud via SlackBuilds-users
Tracking the breakage might require launching the app, or checking with ldd. However, tracking potential breakages could be done using hoorex. # hoorex -i dav1d This'll list all installed packages requiring directly dav1d. - Yth. Le 29 février 2024 16:12:14 UTC, Jim a écrit : >I recently

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Tim Dickson via SlackBuilds-users
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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Arnaud via SlackBuilds-users
Well, you've still got sbbdep then, in reverse mode it could help you. It does calculate a full dependency tree, binary only, so for like python packages it won't work, but in your case it should. I never used it like that though, so it's kind of a guess. - Yth Le 29 février 2024 19:22:49 UTC,

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Alexander Verbovetsky
On Thu, Feb 29, 2024 at 03:22:49PM -0400, Jim wrote: > 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. https://slackbuilds.org/slackbuilds/15.0/libraries/libheif/libheif.info has davd1 in the

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Matteo Bernardini
Il giorno gio 29 feb 2024 alle ore 17:12 Jim ha scritto: > 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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jim
On Thu, Feb 29, 2024 at 16:55 (+), Tim Dickson via SlackBuilds-users wrote: > 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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jim
Hi Arnaud, On Thu, Feb 29, 2024 at 16:53 (+), Arnaud via SlackBuilds-users wrote: > Tracking the breakage might require launching the app, Trying *every* program after upgrading a library seems like a bit of a non-starter. > or checking with ldd. After seeing a complaint appear in my

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jim
On Thu, Feb 29, 2024 at 16:54 (+), Erich Ritz via SlackBuilds-users wrote: > On Thursday, February 29th, 2024 at 10:12 AM, 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

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jim
On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote: > *From: *Jim > *To: *slackbuilds-users@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 >>

Re: [Slackbuilds-users] tracking down SBo "dependencies"

2024-02-29 Thread Jeremy Hansen
On Thu, Feb 29, 2024, 11:46 AM Jim wrote: > On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote: > > > *From: *Jim > > *To: *slackbuilds-users@slackbuilds.org > > *Date: *29 Feb 2024 17:12:58 > > *Subject: *[Slackbuilds-users] tracking down SBo "dependencies" > > >> I recently