Installing sbopkg with Slackware 14.1
One of the more frequently voiced complaints you will hear about Slackware is that it has a limited number of software packages available. There is a fair amount of truth in this claim, as my full install of Slackware 14.1 has just over 1200 packages installed. |
|
|
Comments (12)
Command line equivalents too
I believe almost all of it's functionality is available from the command line. The man pages covers the details.
However, this article was intended as a quick why and how guide for those who don't have the time or inclination to compile their own packages, but would like to expand the range of packages available for Slackware. Those people probably will prefer the dialog/ncurses interface.
This is the first of what I hope to be several Slackware oriented articles, and since some of them will cover software available via Slackbuilds.org, I thought it best to start with a quick write up on sbopkg.
Salix is a very good Slackware derivative which includes sbopkg and integrates it into their package installation options.
Completely understood, I was just adding the comment because I had been using sbopkg for so long and never read the man page until recently and realized I had options :)
> This is the first of what I hope to be several Slackware oriented articles,
Looking forward to them!
Looking forward to more Slack articles!
Number of packages
For example, in Slackware you have exaclty one package for python, in CentOS 7 one python source package becomes 7 binary packages.
But yes, in general Slackware tends to be in the 'fewer packages' category of distros.
Yes. And what is this _dev package other distro's keep talking about? :)
package_name.rpm # for the binary
package_name-devel.rpm # for the build environment. i.e. - all the .h header files that are required if you need to build against this package
package_name.src.rpm # for the full source
Yes, so does Debian, though I don't think they use the same naming convention. Slackware doesn't do that.
But that's the only advantage that comes to mind.
Yes, and Debian goes to even greater lenghts to split a source package (foo, libfoo, libfoo-bin, foo-dev, libfoo-dev, foo-doc, etc) which is specially nice to make a really tiny installation.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Sign up and post (it is free) or Log in and post
