Slackware dev team call - topics of interest/questions?
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.
As an aside, I won't provide grubconfig in Slint64-15.0, as the all-in-one installation script will have functions for that and in the installed system update-grub will be used
In addition I have stolen grub-customizer to Ubuntu for folks not willing or knowing how to edit /etc/default/grub or /boot/grub/grub.cfg and a rescuebootstick maker will be provided.
I will have other things to share, like our big installation script, how to install/uninstall at any time kde, lxqt and xfce with a single command (and optionally hide menu entries specific to a desktop when running another one), how to automatically update the initrd and grub after a kernel upgrade (also with full disk encryption) but will wait until after the relase of Slint64-15.0 to propose only stable things tested on a Slackware64-15.0 base.
Some compatibility way to run software that requires systemd without using some non-slackware version of linux, and without alarming and alienating people.
Last edited by Regnad Kcin; 04-29-2022 at 10:53 AM.
Some compatibility way to run software that requires systemd without using some non-slackware version of linux, and without alarming and alienating people.
I have in my TODO list to investigate how Artix can use dbus-broker without its launcher...
You should probably be more specific, we have grub.
Code:
Looking for grub in package list. Please wait... DONE
The list below shows all packages with name matching "grub".
[inst] slackware64 : breeze-grub-5.23.5-x86_64-1
[inst] slackware64 : grub-2.06-x86_64-4
I think what the poster meant was having grub as an install option with the Slackware installer, which I think would be great.
One can argue that when a new Slackware is released, SlackBuilds.org may not be immediately available with updated scripts for said release. So, I *get it*, that's why I only jokingly asked. However, sbopkg not being available at SlackBuilds.org is a true mystery.
I have provided the source and binary package available on sbopkg.org and it's also available in github, so if anyone want to push it to SBo, feel free
although i kinda think it would be a duplicate efforts
I think what the poster meant was having grub as an install option with the Slackware installer, which I think would be great.
Probably. I've encountered people who get evangelical with things like grub so I figure we should be more specific about these kinds of questions.
I actually would like to know what the roadmap is regarding bootloaders. elilo and syslinux appear to be mostly abandoned and there really aren't really any other options than GRUB.
Please people, there's a separate thread for package update requests: https://www.linuxquestions.org/quest...-a-4175706801/
Let's keep this thread here reserved for possible topics to be discussed by the Slackware Dev team in their podcast!
Ooo, I'll definitely need to make some time to watch this when it's released!
My questions:
Are there any plans to have a public facing distributed version control system (à la a public git repo)? Alien Bob's is nice, but it can be delayed from when updates are pushed out and it could be nice to submit proper pull/merge requests when issues are found, which can be better monitored instead of being potentially forgotten in the "Requests for -current" thread.
What are the future plans for monetization to keep Pat funded and Slackware alive? Patreon is obviously beneficial to keep a monthly flow of money, but are there plans for merch beyond the cafepress store (and hopefully a hat with the classic logo for us folically challenged people)? Plans for stable release DVDs or thumbdrives?
I know that Slackware has always had a "release when it's ready" mentality, but after having an almost 6 year gap between 14.2 and 15.0 with a 2.5 year gap between 14.1 and 14.2, are there plans to shoot for a closer together releases or keeping them further apart? At one point, we were consistently seeing around 2-3 stable releases a year. I don't see that as being beneficial nowadays, but obviously 3-5 year gaps are difficult to keep software up-to-date enough to build some modern 3rd-party software. Is there a rough target you're shooting for of maybe a release every 1-2 years?
Is there an expected target length you're shooting for to support stable releases? We're going to be hitting 10 years of support for 14.0 this fall (which is incredible!). Are there thoughts on how to determine when you'll EOL a version? After a certain period of time? After there are a certain number of stable releases in front of it?
And I just wanted to send out a heartfelt "Thanks!" for everyone involved, including Pat and dev team, as well as all the other contributions via forum and email... all of which make Slackware my preferred distro.
Last edited by bassmadrigal; 05-02-2022 at 05:57 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.