Took the Slackpill - How do I get started
 

Previous user of Debian seeking for a stable base, a well maintained repository and a sane init system. Slackware is right up my ally, but I am aware it's a lot more difficult to maintain by default than Debian. I have a few questions to help me get off the ground

1. ...:redface: How do I enable Slackbuilds? I tried their website's HOWTO but it looks like a bunch of gibberish to a Debian user. I did my best to search what all it meant and all I really understand now is what a build environment is. Is it just like installing a normal package? Explain like I'm 5 how to enable Slackbuilds

2. Can I install a slackbuilds package with slapt-get in some way? Or will I have to use pkgtools (Which is fine with me)

3. As a mirror for slapt-get (and pkgtools) would I just have to put in the mirrors file, as an example, https://mirrors.kernel.org/slackware/? Or will I have to put in a more specific name like https://mirrors.kernel.org/slackware/slackware64-14.2/?

4. Anything else I should know about Slackware? I am prepared to put in a bit more effort than Debian, so don't worry, I know what I'm getting into. I have a ThinkPad X230, any problems I might face or additional drivers I should install?

Sorry if this has been a bit rambly or easily solvable. Believe me, I've tried DuckDuckGo'ing all of these with no success. :newbie:

For 1. Go to www.sbopkg.org and change to the Download tab. There is a link there to download the latest sbopkg. Download it to a convenient location. The command to install it is there. 'installpkg packagename' and press enter, as root user.

To run the program, in a command prompt, as root, type 'sbopkg'. The only thing I suggest is to check the repo that is selected. 14.2 is the latest, in the event you are running current ( not for people new to Slackware ) there are other locations to get slackbuilds from.

Sync the repo, there is a button for that. Then you can select a package(s) you want to install. There is a Docs tab, read it.

I can't help with slapt-get, I have never tried to use it.

Yes, this link has lots of useful information on Slackware.

-->https://docs.slackware.com/start

Thinkpads are usually well supported. There are lots of users here that own them. If you have a problem with something not working, start with the above link. If you can not find an answer there, post here, with as much information as possible.

Best of luck.

If you are new to Slackware I suggest avoiding slapt-get and slapt-source. I use sbopkg for SlackBuilds.org. The main sbopkg commands you will want to pay attention to are:

• sbopkg -r syncrhonizes your machine with the latest 14.2 SlackBuilds
• sqg is a utility that allows you to build queue files, which allows sbopkg to follow a build order for SlackBuild dependencies.
• sbopkg -i allows you to install a specific single or set of SlackBuilds
• sbopkg -i requires double quotes if feeding a list of packages: sbopkg -i "package1 package2 package3"

If you need more information than that, check out:

• sbopkg --help
• man sbopkg

sbopkg docs: https://sbopkg.org/docs.php

---
For managing Slackware official packages, see the slackpkg documentation:
https://docs.slackware.com/slackware:slackpkg

I use sbotools . it's as easy as
It resolves the deps for you and installs them and the package you're wanting installed. Providing it is in the repo you're using, it defaults to slackbuilds.org. then if you find something that is not done already in slackbuild or AlienBoB, or Ponce (current 14.2) you can get the templates off of slackbulds sight and make one yourself. Its not too hard to figure out for most.

Except sudo is not setup by default in Slackware. That's another step.

While I think that tools like sbotools and sbopkg are very useful, I also think that working through a SlackBuild manually should be a required learning experience. That way a person has a grasp of how SBo works.

Agreed.

I totally recommend that, too. It can be quite overwhelming at first, but after a few builds (with dependencies) I got a understanding of how slackbuilds work. VLC especially, but I wouldn't recommend that as a first try.

OP does have prior Linux experience, so adding the extra helpful sudo command is not a bad thing. even if op didn't have prior linux experience. and did you read that OP, do not deprive yourself the experience of running slackbuilds one at a time so you know how it works. :D I'd then further suggest he downloads the source and make his own slackbuilds first, before it moves on to learning how to use Slackbuilds.org, then moves on to sbotools or sbopkg. a set learning progression is good yes?

Sure, but if I remember correctly Debian has sudo set up out of the box. I don't setup sudo on Slackware, seems like just an extra step when it's just as easy to su and exit.

I don't know about making a SlackBuild first, unless of course the user has at least some experience compiling from source. There are options that can be changed and the rare occasion that you may need to patch something. However it is good to learn to compile from source and learn how to create a Slackbuild.

su or sudo or su - or just logging in root account, that actually falls under user preference.

you've never even compiled from source yet? :tisk: what have you been up to? ;)

its easy to edit ones sudoers file.

slackpkg: https://docs.slackware.com/slackware:slackpkg

Do you need multilib? If so:
https://docs.slackware.com/slackware:multilib?s[]=multilib

I use slackpkg+ in order to keep Slackware official packages, multilib, and ktown (Plasma 5) up to date.

Me? I laugh at your assumption.

https://github.com/CinSlack/cinslack

I made the switch from Debian to Slackware a few years ago when the init system that shall not be named was added to Debian Testing. The whole Debian ecosystem was in an uproar and I had to unsubscribe from the Debian-users mailing list for a time due to the constant infighting. Mind you this was before the user base knew the exact fallout of the change. You have come to the right place. :)

At first you will think that Slackware is more difficult to maintain. Once you learn how Slackware works, you will find you are in more control over your system, and actually get things done more quickly. Rebuilding a package or customizing your system in/with Slackware is so much easier than with Debian. Debian takes the approach of a "one size fits all" and Slackware lets you tailor it to whatever size or shape you wish.

A while back I met up with a friend of mine who also used Debian for a time and found it difficult to compare Slackware to Debian because the design and philosophies are so different. As a Debian user it will be a bit intimidating to know you have so much control. Ride the wave, post your questions here on LQ, and don't be afraid to try things. If you read the Slackware documentation (and occasionally the man pages) it should be pretty hard to break your Slackware system.

If you are looking to get an apt or apt-get drop in for Slackware, the simple answer is there is no such thing. apt, apt-get, aptitude have many different features you will not be able to find in Slackware. I am not trying to take anything away from the valuable work done by the author of slapt-get, I am just speaking from my own experiences as an ex-Debian user.

my bag, I misread that post, eye ball typo. :D

@kr4k3n: Based on the nature of your questions, you might be interested in an intermediate step into Slackware. Use the Salix distro, a derivative of Slackware that adds some admin GUI tools, including a GUI package manager.

The Salix folks use slapt-get and gslapt, which is a GUI front-end to slapt-get. Generally slapt-get and slackpkg should not be mixed. The Salix folks provide support to enable trusted third-party repos that provide premade binary packages rather than learning to build packages from slackbuilds.org. The design of slapt-get is much like apt-get and gslapt is similar to the GUI Synaptic package manager.

Many long-time Slackers do not think twice about compiling packages. Compiling packages from slackbuilds.org is not horrible but to somebody unfamiliar with the idea, the approach seems like stepping back into the 1980s. Salix will provide a way to get familiar with Slackware. Later, down the road, take a wack at compling a package from slackbuilds.org. :)