Sugeestion: -current: merge patches from archlinux
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.
Slackware-current is not a rolling release like Arch Linux.
Instead, the Slackware-current is the development tree of Slackware and NOT for the users but for beta-testers, and of course it has moments when it is unstable, because the additions of new software.
as my experience, archlinux is stable than -current
Which patches do you think could be merged? If there is a problem that needs fixing and arch has a fix then it might be merged, but unless these problems are pointed out then there is nothing to do here and intentionally or not your post is troll bait.
Slackware-current is not a rolling release like Arch Linux.
Instead, the Slackware-current is the development tree of Slackware and NOT for the users but for beta-testers, and of course it has moments when it is unstable, because the additions of new software.
Yes. Furthermore Arch is not always stable (which is to be expected for a rolling release). As en example recently an upgrade broke the Orca screen reader, preventing blind users who applied it before a fix be provided to access their desktops, see the the thread beginning with this post.
Last edited by Didier Spaier; 09-02-2018 at 09:19 AM.
Furthermore Arch is not always stable (which is to be expected for a rolling release).
I run Slackware64-current and Arch(virtual machine). Both distributions on occasion break. In my experience Slackware64-current is more stable than Arch. YMMV.
please do not angry: if we wait everything fixed by upstream, we will never got a stable release.
it has already been asked you but you still haven't minded answering: which are the patches that you suggest to merge and to solve which particular issues, exactly?
it's not clear reading your messages and the links you provided.
glibc-2.27 has been provided for -current since February 9, 2018, 8:59 PM and mesa 18.1.7 since August 25, 2018, 1:06 AM as you have acknowledged in these threads.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
