If you're just starting out with current, definitely give here a read, too, before updating. That way you can get a sense of the type of breakages that occur. For instance, there was one update to pango that broke menus. Another update to alsa broke pulse. They were easily fixed, but it's the kind of show-stoppers you might encounter. Also, when we had the big rebuilds, there was a specific order one needed to upgrade in, otherwise you could get into a situation where pkgtools wouldn't work, if you upgraded them before glibc, for instance.

Things breaking in current are rare, but they do happen, since it's a develolpment release.

2 members found this post helpful.

Indeed! It's always a good idea to read the current changelog *before* you update your system. Mr. Volkerding will carefully document gotchas in the changelog that you can avoid.

http://www.slackware.com/changelog/c...php?cpu=x86_64

There are many of us who are beta testers and we'll report breakage here and also possible fixes. This forum is a valuable resource.

1 members found this post helpful.

What is best way to install python libraries in current??? Slackbuilds or pip??

There will be differences of opinion here. My practice is to use SlackBuilds.

this is not something that differs if you use stable or current: if you need the python libraries system-wide you better install them via SlackBuilds so that everything you install in the system is tracked, if you need them for a single user you can also use pip2/pip (python-2.x or python-3.x) to install them in your home.

but, IMHO, before doing the jump you should consider that Slackware current is the development version of Slackware and things may break or may require fixing: if you decide to use current it's assumed that you should be able to take care of these issues yourself.
if I were in your position I would try to install current in a virtual machine first, update it for a while and then, only when you feel confident enough, switch to current.

2 members found this post helpful.