The -current Slackware builds support nvme, but the 14.2 base does not. I found a thread on another forum (about 4 pages long). You can dig through the whole thing, but at the end of it, one person summarizes to follow the simplified steps in his post here. It describes a UEFI setup, but also says you can simplify it further if you choose BIOS (Legacy) mode instead. The same person also offered this link to Alien Bob's blog with detailed instructions for a UEFI install.
Slackware, Arch, Gentoo, even Debian (if not using non-free edition).... these can be difficult, but you can learn a lot if you can manage to get them up and running (and keep them running). But this struggle is why Ubuntu and Linux Mint have come into being... for lazy people, like me.
Basically yes, there are a couple of Caveats which i might get to later .
lets take an example. there is a command in slpkg :
# slpkg repo-enable
//that allows you to pick repo's that have packages; but its a gui so you need
that is available via sbo and i think thats a default repo in slpkg.
So try this: # slpkg -F python2-pythondialog
// F is the find flag, you should see on executing this command that , that packge is found in sbo .
To install it use: # slpkg -s sbo python2-pythondialog
sometimes its a small effort of trial and error due to deps on one package being replaced when you install a new package and it replaces a "common" dep but maybe older version. Really i've had next to no trouble with it .
the small caveat is that say when you build "clamav" during the build it will tell you , you need groups setting up before the build. So i usually go to slackbuilds and read the read me. eg clamav at slackbuilds says for clamav:
what i can say is that I have been running current for a few months now using exclusively slpkg , couple of small trial and error , when one package from one repo didn't work i just removed it , with deps and tried another. I have chromium, clamav, libreoffice5, cinelerra , geany and a few others and all installed seamlessly.