Well, even though -current is "not stable", it is by no means an unreliable mess either! It is probably worth trying to understand and fix the problems rather than reinstall and say it was due to 14.0.

1 members found this post helpful.

You may stay with Slackware current, provided:

- you read carefully the changelog for it (see my previous post) before applying any update
- to update, unless otherwise stated in the change log you apply the method recommended in "man slackpkg" for updating current
- you be aware that as it is released for testing purposes, something could break unexpectedly after an update

Only you can decide if you are ready to take the risks.

1 members found this post helpful.

Ok, now what about SlackBuilds and sbopkg? I've been using sbopkg to install a lot of things, and on SlackBuild site there is only 13.37 no current option. So am I ok to use sbopkg and SlackBuilds still?

Thank You All. This really helped my newbness. This will solve a lot of problems now that i have correct mirror for slackpkg and know im using -current and not 13.37

Despite the pain of reinstalling, if you started with -current and then used slackpkg with a 13.37 mirror to do updates, there's honestly no good way of telling what you actuall have installed on your machine package wise. I would suggest reinstalling with 13.37 and going from there. Just my two cents, but my view is that troubleshooting becomes infinitely more complex when I can't even trust the foundation I'm building on. Doing a full bore update to 14RC1(aka -current) is another option, but if you don't yet really understand package management and version numbering in Slackware, -current might be a can of worms not worth opening just yet.

Thank you, that is good advice. I am going to keep -current for now, because the whole point I installed Slackware in the first place is to learn, and so far I have learned a lot more than when i was using other distros. A lot of problems I have been figuring out and researching myself which is really helping me learn. Thanks for your input

1 members found this post helpful.

About slackbuilds.org and sbopkg: no, you can't use it on -current, they are only intended for stable releases.

Regarding trusted sources of packages and slackbuilds though, you can have a look at Alien Bob packages. Some of these are available for current or can be installed on it, see the file ChangeLog.txt.

Your problem is this:

Code:
root@reptaur-/var/log/httpd# cat /etc/slackware-version
Slackware 14.0
root@reptaur-/var/log/httpd# grep '^[^#]' /etc/slackpkg/mirrors
http://slackware.mirrors.tds.net/pub...ackware-13.37/

If you've done a slackpkg update with that mirror, you aren't running -current. You are running a hybrid that you probably can't identify. If you've only used slackpkg to reinstall httpd and php, you can fix it reinstalling the appropriate versions of these two packages. However IF you have done a slackpkg update install-new upgrade-all clean-system then you have a potentially serious issue. You need to make sure to select an appropriate mirror in /etc/slackpkg/mirrors for te version that you are running.

Sbopkg and slackbuilds.org are generally fine on current, but there are likely going to be many packages that will take much effort to get to build on -current, because of upgrades to the dependencies you have installed with -current.

Either way, to each his own and have fun!