Unless you're not in the US in which case it may be a more efficient use of your money to simply make a donation as a "thank you" for the free download (postage costs can be truly horrific).

1 members found this post helpful.

Crickets chirping. Our OP still only has 2 posts. He is not responding

A SlackBuild is just a shell script that creates a Slackware package from a source archive (or from a binary archive even, like a .deb/rpm). If you look in the source directory of a Slackware mirror you will find SlackBuilds. Slackbuilds.org (SBo) is a community driven repo of SlackBuilds (with some extra metadata files) for stuff that is not in the base Slackware distribution.

The manual way is to download the SlackBuild and associated files, download the source, and then run the SlackBuild itself (either chmod +x and run it or just sh file.SlackBuild). That would produce a Slackware package that you can install with installpkg. However, it's much easier to use an SBo management tool. Personally I find sbotools to be the least hassle, but sbopkg is very popular too.

I can't comment on slapt-get, since I've never used it (might be fine, but it doesn't seem necessary to me).

There has been some very good advice in this thread. Unfortunately I think this has been somewhat counterproductive and the OP has been slightly overwhelmed with information. He says he is willing to put a bit more effort into Slackware than Debian, however, from my experience as a co-Debian user, Slackware needs a lot more effort, especially if one is not coming from a Unix background.

This is good advice.

This is what I like about it!

Yes, this is a particularly worrying thought process. It is not possible to explain difficult concepts as one would to a five year old so that not only can the five year old understand them but reproduce and apply the advanced knowledge. If this were the case we would all be neurosurgeons.

Take a look at the video

Blockchain Expert Explains One Concept in 5 Levels of Difficulty

and you will see that in order to understand advanced concepts, one must build up levels of understanding. Not only this but a lot of info must be omitted from basic explanations so as not to confuse the listener. Groundwork has to be done. In order to fully comprehend making a SlackBuild, understanding of various functions is necessary, such as the tar function and the chown function. These are not functions one needs to perform often - if at all - in Debian. Certainly I've never had to use them in Debian, but Slackware I have to often.

Nevertheless, for entertainment purposes I will attempt to explain making and installing a Slackbuild in incredibly basic terminology. I will use neofetch from slackbuilds.org as an example.

1. Download the source file and the Slackbuild. Navigate to the Downloads folder with

2. Create a folder called neofetch, unzip the Slackbuild file and place the contents into the neofetch folder you just created. This can be done with the command

3. Move the source file into the neofetch folder with

4. Navigate to the neofetch folder

5. run the SlackBuild as root with

6. When finished, the Slackbuild will automatically be dropped into the /tmp folder, so you'll have to navigate there with

7. As root install the package with

Now if that's not simple enough I don't know what is.

Perhaps we scared him off with it enthusiasm, and how he's wondering if he got himself into some weird cult.

(Okay, if anybody feels the need to say "Praise Bob," keep it on the down low for a little bit.)

2 members found this post helpful.

Maybe that's what I've been doing wrong all this time. I need to invoke the dark arts in order to solve some of my issues.

Easy: never ever change inittab's runlevel, and enjoy the dark light of the terminal. To reach the command line, just follow the pipe. Banish all rodent from your desktop, and dive into the power of ascii.

1 members found this post helpful.

Well indeed. But yes, from the standpoint of manual compilation...

for Lysander666 post #34, some slackbuild have multiple source, like openjdk

after should get all the source files

2 members found this post helpful.