SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Things breaking in current are rare, but they do happen, since it's a develolpment release.
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.
What is best way to install python libraries in current??? Slackbuilds or pip??
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.