Okay right off the bat, and in order to keep the hair rising up on anyone's back, thinking there's an sbopkg
bug or something - this isn't about that...
works great and I've had not issues with it - aside from issues that have manifested as a result of SBo issues or the upstreams.
k. Basically, I'm chronicling the convoluted way I had to install some software using sbopkg
, how it helped and made dificult installations easy, and how I overcame some of the brickwalls that I came up with.
The particular application I'm going to focus on is *Shutte
The thing I should probably bring up now is how wonderful *sbopkg
* is, and also what a dream it has been to work with.
is kinda like the *Slackpkg* for the 'unofficial' SlackBuild repository, rather than the official Slackware repositories for software released w/each stable Slackware version.
Anyone who has ever used *slackpkg* will feel right at home with *sbopkg
* - although they operate differently, they achive a similar end result - Slackware packages installed/upgraded on your system.
Yes, we've all gone out and d/l'd a package and performed an upgradepkg manually following an annoucement to the slackware-security list.
*slackpkg* automates this process.
automates the process of downloading an SBo, the source tarballs, the build process, and even the installation of the resulting package.
The ncurses based interface is familiar - like the Slackware installation setup program.
In it's default state, you simply pick the applications, place them into a queue (in the order of their deps) and voila! a new item appears in your menu in a few minutes ready to execute (or not, if it's not a GUI app
For more background information on sbopkg simply visit the project page and view the man pages at: sbopkg.org
My problem began when going kinda koo koo for coconuts after installing sbopkg
. Yup, like a kid in the candy store I started going after those apps with an endless train of deps that otherwise would take the better part of a day to accomplish an install.
Using the browse and search functions, you can easily get through organizing your deps much more quickly through the curses interface than you can at slackbuilds.org
As long as you've got your pen and paper with you, simply add everything to the queue, because later you can sort that installation queue in the order the deps need to be installed
Okay, with a pile of "perl-xxxx" packages needed, amongst other packages, Shutter
I hit the wall during the processing of the queue for this software, being unable to get a few packages, itemized below (at this point, since I went koo koo for coconuts, I can't be sure that these were actual dependencies for Shutter or not, since there were so many apps I queued up at one time, but the kludge will hopefully be a valuable tool for getting past the impasses).
Here's a couple of highlights. I had errors like, 404's and no route to hosts, changes in source tarball names, etc...
I'm a little tired, but for some reason the whole slackbuild thing just didn't happen (can't remember why actually).
I did a search for the package itself at SlackFind.net
, and found "perl-gtk2-1.222-x86_64-1jsc
After a quick d/l (and inspection of the package
) I simply ran installpkg and then the modules depending upon that installed just fine until...
This module depends upon 'perl-http-response', which bombed, so I begin looking for it.
I checked Slacky.IT (which is now Slacky.EU)
, and nothing, and then I started scratching my head, wondering why I'm installing Slackware packages for Perl modules - what's the benefit to that? hm...
Well I figured I'd just fire up 'cpan' and do an:
cpan > install HTTP::Response
kewl... Then I removed perl-http-response from the sbopkg queue and fired off another process of the queue...
perl-httpd-response-encoding installed just fine. But now I'm really starting to wonder why I don't just install ALL of the Perl modules this way?!?!?
This needs perl-xml-twig, which, as you might have guessed, bombed. I could only find i686 versions at Slacky.IT and Slackfind.net, so again....
cpan > install XML::Twig
kewl, perl-net-dbus installed fine through sbopkg now
had that not worked, I could have compiled the Perl modules by hand I suppose (sometimes cpan just won't get you there).
Shutter is pretty kewl.... Full featured and I needed the bells and whistles it provides for creating some tutorials, where other screenshot utils would require me to save the shots and then Gimp 'em.
It's nice doing it all in one step.
Well this was basically just a demonstration of a kludge to work around broken upstreams when using sbopkg, but not really - it's more about SlackBuilds, but not really - it's more about hunting down source and packages when upstreams are offline, to resolve dependencies, so you can interupt an sbopkg queue, take corrective measures, and finish up your queue once you've gotten through that one little package in the middle of the dep list you need first!
What is the purpose of installing Perl modules via Slackware Packages? why not just use Cpan for all of that instead?
I dunno, aside from the official release packages, I would think that Perl modules would be an exception to using SBo's, deferring to cpan instead, or perhaps even just compiling those Perl mods by hand.
That would be keeping the slack stuff w/slack and Perl with the Perl - right?
Weigh on in anytime you like
In the meantime I hope this helps someone who gets stuck in the middle of wanting to install something.