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.
I'm new to Slackware and I'm honestly curious what the stability of -Current is in comparison to the actual Stable release. I chose stable because I wanted a rolling release system, not based on stability.
I chose stable because I wanted a rolling release system, not based on stability.
There is no such thing as a rolling release in Slackware. The official release of Slackware reflects a collection of software versions that combine to provide a stable environment that can be relied on to perform without issue. That is the Slackware hallmark.
Quote:
I'm honestly curious what the stability of -Current is in comparison to the actual Stable release
Slackware-current is the development version of Slackware. It is unusual for Slackware-current to cause major breakage, but it has happened, and is generally rectified in a very short time frame. If you run Slackware-current, then it is expected that you are prepared to identify and suggest changes that will address any problems that you see.
I'm new to Slackware and I'm honestly curious what the stability of -Current is in comparison to the actual Stable release. I chose stable because I wanted a rolling release system, not based on stability.
Having used -Current for years, it's very stable, more often than not as stable as official releases.
Usually the software included in Slackware will be stable in -current. However, -current can and will break your 3rd-party packages when core components in Slackware are updated (which still tends to not be very common). All that is required is to recompile those packages to use the new core libraries.
You may also run into issues with 3rd-party scripts, like SBo's in that they are only tested for the stable version and some require changes when updated software is introduced in Slackware.
I wouldn't suggest -current if you're not very familiar with SlackBuilds, dependencies, and how to work through any problems that come up.
If you're using current, then once in a while, you'll have to rebuild some of the packages that you built from source. If you stay with the release-versioned repositories, then that will never happen.
I'm new to Slackware and I'm honestly curious what the stability of -Current is in comparison to the actual Stable release.
I'm running -current on 2 out of 5 Slackware stations and 14.2 on 3 stations. From my experience -current is stable. On rare occasions -current breaks,but, a fix is not long in coming. If you run -current it is expected that you will be able to trouble shoot issues if they arise.
what Dugan said: Almost as stable, but, if problems happen, don't get bent out of shape: remind yourself that that can happen when you use a testing distro.
I've encountered two significant problems over the five years or so that I've been using --Current. Somewhere along the line about three years ago, digikam stopped working (I was using the one from Slackbuilds.org). I got into the habit of just jacking the SD card into the computer and don't miss digikam any more.
More recently, sometime last year, some updates broke Libreoffice. I use AlienBob's LO package, and there was a delay of a few days before he got an updated package ready for download. I don't have to use an office suite very often any more, but I fell back on using Calligra in the interim. I hadn't used it before, so I told myself it was a learning experience (it was, too; I learned why I like LibreOffice.)
I'm sure other persons have encountered other issues, depending the software they need to use.
[...] I fell back on using Calligra in the interim. I hadn't used it before, so I told myself it was a learning experience (it was, too; I learned why I like LibreOffice.)
I just learned that coffee through the nose is still painful.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.