Great :-)

I can add: you free to use 14.0 branch of SBo for your 14.1 instances. 99.9% packages will be buildable and will work as if they built on 14.0, unless they are really broken. Mainly they can fail because of outdated source links, but in this case they will fail to build on 14.0 either. If you meat such packages and report them here, directly to maintainer or into SBo maillist, you will get solution quite soon(sooner than if you wait until whole 14.1 branch will be declared stable/ready).

Well the only one I have tried and had issues with so far is vlc. I can't remember what package it said it was missing. I went to slackbuild.org and looked at the vlc package they had. The dependencies where underneath that so I tried to install those and a couple didn't work with sbopkg. Sorry I can't specifically remember which ones at the moment. I didn't write them down because I was going to try it again later.

Just a minor warning. If you use cfdisk on an unpartitioned disk it will create the first partition beginning at sector 63 of the disk. This is OK for older mechanical disks, but not for disks with 4K sector size or SSDs, since your partitions will not be aligned to the physical sectors. This can give you serious performance decreases on write actions. If you happen tu use such a 4K disk or a SSD I recommend to use fdisk instead of cfdisk, fdisk defaults to aligned partitions.

1 members found this post helpful.

Regarding to dependencies of packages on SBo.
User must manually resolve all dependencies before build packages(well, Slackware-ish way), since .SlackBuild is ordinary shell script which responses only for building certain packages.
sbopkg - relatively simple tool which allows to run .SlackBuild's a little comfortably. sbopkg does not analyse .SBs for dependencies, caveat's, special cases.
However sbopkg provides mechanism to help user to build packages with dependencies. It is called Queue.
queue file is list of package names(names only, no categories) within SBo repository. This list also defines order of packages to be build, so dependencies will be built first. This list also can contain reference to other queue files. sbopkg merges lists of packages of referenced queues and list of packages in current queue(order kept, duplicates removed).
So, instead of build packages vlc directly, you can create queue file which contains a list of dependencies, and itself vlc package at list tail. Then you can load that queue into sbopkg and start to build it. (NOTE: each package built independently, so if one package fails to build, next will be started)
There is repository of ready made queue files anybody can use. You can clone it or download packaged snapshot, put(unpack) it into your local queue storage and use it. However I advice you to check manually list of packages to build, since it can be pretty long and time consuming(one queues contain only required dependencies, other both req. and optional).

PS: VLC. You also can download and install pre-built package for your Slackware version by Alien Bob

I have gotten so use to not doing things like this. With Fedora or Debian things are all there, almost everything I need or want. The only thing I compiled recently (more or less recently) was Wine when I was using Debian 6. I liked to keep up with the latest and greatest of their releases. Fedora I never had to bother. The current Fedora was so close to the actual Wine Dev that I didn't need to compile it anymore. I look forward to learning things the Slackware way.

I will check out Alien Bob as well. Since I am new I was worried that I would get the wrong repos. I would rather go without than install something that is unkown to me and may be dangerous or destructive.

I did try the sbopkg queue with the dependencies. I still got an error with one of the packages neededing another. I searched, though it was a fast search, and couldn't find it. Shortley I am going to boot back into Slackware and add Alien Bob's VLC and the repo. Than a few other things as well. Just the basics for now like flash (nonfree, Gnash is up to it yet for me,) openjdk/Icedtea, etc. Than I need to add Fedora to the Lilo boot menu. It picked up Windows nicely, well Fedora/Grub does to, but I want to get use to Lilo. Been awhile since I tried it and even than it was briefly before everyone, just about, went to Grub. Lilo will be fun to learn.

Thanks for the tips and link.

I want to thank everyone for your help, thoughts and getting me started in the right direction. I am at the point now where I will be taking my time and learning Slackware as I go. Which will require, at times, searching and researching. I think I will be do it without asking questions, unless something major happens. It is more fun that way and a better way to learn I think.