Continuing with the series of articles that try to demystify this great distribution, it is time to present what from my perspective is the simplest way to install packages within Slackware, it's about the SlackBuilds and a small application that it simplifies us even more life when managing them, Sbopkg.
It is worth mentioning that this tool DOES NOT resolve dependencies like most tools for SlackwareHowever, this can be a very bearable task, as we will try to explain later.
What are Slackbuilds?
First it is necessary to mention that the "traditional" way of installing packages in Linux it is compiling from source code, which in general works but can present itself as a future problem, for example, when an already installed package tries to update and the system administrator (you) forget compilation values.
To avoid this type of inconvenience in Slackware the decision was made to use a script to automate the installation process, in such a way that to install a new version of each package, all you have to do is modify the variable that informs the system about the version of that package.
To this collection of scripts they were called SlackBuilds and they are to say the least, absolute ones blessings sent by the almighty God Tux for all those users who did meditation for weeks to reach the level of enlightenment that led them to use Slackware (My mother says I have a lot of imagination) ...
The way to use them is very simple, first we go to the page where the complete collection of Slackbuilds packages is located, it is about http://slackbuilds.org/.
and we use its integrated search engine to locate the packages we need, for example let's search "Flash", so we will get a list of packages that match the search.
For this case we will choose to install «flash-player-plugin«.
We will get package information that we choose, for example, its version, a brief description, its official page, official download links from where we will obtain the source code in its available architectures and a download link to the SlackBuild who will take care of the installation process.
We downloaded the source code and SlackBuild.
We extract el SlackBuild.
We move el source code (uncompressed) within the directory of the SlackBuild that we just extracted.
We open our comfort in the directory of SlackBuild.
Now we will create the package installable, but first it is necessary log in Be root.
For, architectures de 32 bits we type «. /flash-player-plugin.SlackBuild ».
For, architectures de 64 bits we type «ARCH = x86_64 . /flash-player-plugin.SlackBuild ».
The process of packaging and if everything went well in the end he gives us the rue where the package created, in this case it is "/tmp/flash-player-plugin-22.214.171.124-x86_64-1_SBo.tgz".
Now subtract install el package by tool which Slackware provides us for this task (in a later writing these tools will be discussed in depth), is installpkg.
We type "Installpkg /tmp/flash-player-plugin-126.96.36.199-x86_64-1_SBo.tgz".
The process of installation and if everything went well, it tells us that the package has been installed.
As can be seen, the process not so complicated, although yes could result slightly tedious In principle, for example, what happens if the package we want to install requires a large number of dependencies, the procedure of downloading each SlackBuild and every Source it could make more than one decide to abandon the distribution.
Fortunately we count and with a tool that can greatly simplify the task of install applications, although I insist, don't resolve dependencies, "Sbopkg".
sbopkgIs a tool en Command line which this synchronized with the repository de slackbuilds de slackbuilds.org (SBo), in such a way that if we want to install a package, we must first go to slackbuilds.org to check that it is available, as well as to verify its correct name and the dependencies that it needs.
Using of example installation previous, «Flash-player-plugin», we will notice the difference.
Just enough key "Sbopkg -i flash-player-plugin".
Final report: DO NOT it is necessary that we download neither the SlackBuild nor Source, since this tool takes care of everything.
we confirm what do we want to install typing «P».
And we will get the package ya installed for whatever our architecture.
Final report: Previously we must have installed sbopkg (Process detailed below), this application is used in the console and it does not care what directory we are in.
For, install sbopkg we must go to its official page discharge y get it
We open our comfort in that directory and we type "Installpkg sbopkg-0.36.0-noarch-1_cng.tgz" (Let's not forget that should to be Be root)
And we already have installed sbopkg.
Once installed sbopkg, the first thing we should do is synchronize su basis de data with that of slackbuilds.org, for this we type "Sbopkg -r".
Once completed la synchronization, we are ready to install may be made by each package available through sbopkg.
To carry out the management de packages through sbopkg we have Both of you Options, the classic line de commands or by sbopkg at their interface ncurses.
It was already seen in the example previous the way of install un package with sbopkg en line de commands, but what if we want install un package which require dependencies, to avoid installing each package independently, we could specify all the packages to install within double quotes (").
For example, for install "Supertuxkart" requires two dependencies, "OpenAL" and "irrlicht".
So instead of typing each package by separate, we type in a single line 'sbopkg -i "OpenAL irrlicht supertuxkart"'.
Final report: Let's observe how each package is separated by a space and the set of them is enclosed in double quotes («).
So we will obtain supertuxkart with its dependencies covers.
To get one complete list the Options of package handling that allows us sbopkg, enough with key on the console man sbopkg.
La another option that offers sbopkg, it is by using its interface ncurses. To access it, just key "Sbopkg" in our console.
As will launch a interface where we can observe we have Options that will allow us sync repositories, install, uninstall, to update packages among others, its use is very simple since it is enough to select the options we need.
Broadly speaking, it is the way in which we can have a system Slackware very bearable, if we combine the number of packages available with the installation of Slackware and those available through SlackBuilds we will get a very long list of packages for this great distribution.
There are no more excuses let's use slackware !!! ...