Post by rootPost by RichPost by rootSlackbuilds is my last choice since it doesn't list dependencies of
dependencies.
Oh but it does. But you have to go to the page for the dependency
to see the dependencies of that dependency. Which you have to do
anyway if you want to download the scripts via the web interface.
Tracing out the dependencies is a terrible nuisance. Once you have
done that you have to build them from the bottom up: first you have
to build all the elements which have no further dependencies. Then
you work up the stack to, finally, build the item you started out to
get.
Oh, I don't disagree. It is a royal pain. I've done it myself many
times.
It 'is' something that is almost trivial for a computer to do.
But none of us has come forward with the code to instruct the computer
to do it, so it is still an undone feature.
Post by rootPost by RichWhat it does not do is list the full tree of dependencies at the top
level (i.e., at the audicaty page level for example). Yeah, that
would be a useful feature.
It is a real pain to trace the dependencies for something like
ffmpeg. In most cases slpkg does the job for me. However, in this
case I was put astraddle (I think that is a word) of two version of
qt stuff. Before trying to fetch audacity, I tried an update of
calibre. This involved updating some of the qt stuff. That broke
the requirements for Slackbuilds audacity. Trying to fix that broke
calibre.
Well, short of the software having enough AI to realize that package X
needs qt-vX and package Y needs qt-vY and to install qt-vX and qt-vY in
separate locations, there's not much that could be done here (besides
the software aborting with a message that X needs Y but you have Z
which is used by Q and so upgrading Z to Y will break Q).
Post by rootToday I ripped out anything to do with audacity, and deleted the
calibre from slonly. I fetched a working version of calibre from
Alien. Slonly offers Calibre 3 while Alien offers Calibre 2. I am
guessing that has to do with different versions of Python. My
slackware still runs Python 2.
Yeah, that's Slack's standard python. Python v3 is available in
SlackBuilds (and will install alongside v2), but it is not already on
the install media from the start.