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.
Who knows if this does get addressed - overall it is not a big deal but more of an aesthetic issue. This is regarding two options in the menu during the install of Slackware - "Expert" and "Menu" , and it is even stated in the labeling that they are exactly the same. So it begs the question, why are they both there - and can't one (either Menu or Expert) be removed? If not removed, the very least maybe either Menu or Expert should have the output changed to terse. I rather like the terse output anyways, as it seems quicker to me.
Perhaps also it might simplify the menus, as perhaps it would just cause slight confusion as why are there two choices that are exactly the same, and even have the exact same output when the install is occurring.
After all, who tries to use the expert mode, when the recommended usage is Full Install?
Me - I am that idiot - merely to remove Akonadi.....and other DE/WMs ........and Seamonkey.....and Vulkan since I don't game.... I don't expect this to go anywhere, it was just an observation anyhow about Expert and Menu. Also I never used tags; but I don't think that should be removed - Menu and Expert on the other hand are exactly the same thing so that is why I feel perhaps one should be removed - or again the very least Menu or Expert; whichever, doesn't matter which should at least have the output changed to terse.
I don't expect this to go anywhere, it was just an observation anyhow about Expert and Menu. Also I never used tags; but I don't think that should be removed - Menu and Expert on the other hand are exactly the same thing so that is why I feel perhaps one should be removed - or again the very least Menu or Expert; whichever, doesn't matter which should at least have the output changed to terse.
Well, your observation is correct that those options result in the same behavior.
Hey, also I believe that switching to --terse by default should be done everywhere.
Well, your observation is correct that those options result in the same behavior.
Well it is also stated on the menu selection itself.
Quote:
Originally Posted by LuckyCyborg
Hey, also I believe that switching to --terse by default should be done everywhere.
I also like terse as it just seems to install quicker as it is not displaying the information about said packages, but thats just me. Maybe though FULL can just keep the output as is, but the very least Menu or Expert should have a different output to at least make it somewhat different, because right now it is exactly the same thing whichever you choose, and it just feels like a waste imo.
Well it is also stated on the menu selection itself.
I also like terse as it just seems to install quicker as it is not displaying the information about said packages, but thats just me. Maybe though FULL can just keep the output as is, but the very least Menu or Expert should have a different output to at least make it somewhat different, because right now it is exactly the same thing whichever you choose, and it just feels like a waste imo.
I do support this if I understand what Jeebizz proposes.
If this goes to a vote as I think it should, then I vote to support this motion.
However I suggest that it be done for the next iteration (i.e. after 15.0 has had a chance to stabilize.
If Slackware is already in beta then nothing new stuff should be added that's the rule. If not in beta then ok slip it in. One more change request won't hurt, it is a simple change as you say.
If Slackware is already in beta then nothing new stuff should be added that's the rule. If not in beta then ok slip it in. One more change request won't hurt, it is a simple change as you say.
Did I just say that? I sound like a dictator! Sorry.
Since it is in beta I feel the point is moot, this is just a change to the installation menu and can technically happen, its not like it is in RC status yet.
Since it is in beta I feel the point is moot, this is just a change to the installation menu and can technically happen, its not like it is in RC status yet.
NOT yet. After there's the new kernel and new GCC adopted, will be.
NOT yet. After there's the new kernel and new GCC adopted, will be.
Well....
Quote:
Tue Apr 6 19:54:52 UTC 2021
Thanks to nobodino and ponce for help fixing a few sources that wouldn't
build properly. Overnight I tested recompiling everything using gcc-10.3.0-RC
and had no build failures, so we'll be taking gcc-10.3.0 once it (and new
kernels) arrive probably sometime next week. And then I think we'll be calling
this a beta. Cheers! :-)
-edit
or I may have misunderstood - perhaps it is not even in beta yet since it hasn't been adopted - which in that case it is still moot - I don't see why the installation then couldn't be altered. Either way, its not a big deal in the grand scheme of things - as I stated it is an aesthetic observation.
However I suggest that it be done for the next iteration (i.e. after 15.0 has had a chance to stabilize.
This is strictly an aesthetic change and wouldn't affect the stability of the OS.
Quote:
Originally Posted by ctrondheim
If Slackware is already in beta then nothing new stuff should be added that's the rule. If not in beta then ok slip it in. One more change request won't hurt, it is a simple change as you say.
As LuckyCyborg and Jeebizz pointed out, we're not in beta yet (but close). However, beta has not been a tag that has prevented Pat from adding things to the distro. After beta1 was announced for 14.2, we saw 4 programs added to the main tree (gtkmm2, gparted, hexchat, and libcap-ng) and additional things added to testing/ (kernel configs, tmux, screen-4.4, and kernel-module-ecryptfs). Screen-4.4 ended up getting upgraded to the main tree before release.
I do think that Pat tries to minimize adding things once beta hits, but I don't think he's against it if the addition makes sense and it's not likely to be too disruptive.
This is strictly an aesthetic change and wouldn't affect the stability of the OS.
As LuckyCyborg and Jeebizz pointed out, we're not in beta yet (but close)
Ok, we are now in beta:
Code:
Mon Apr 12 20:07:12 UTC 2021
I'm going to go ahead and call this a beta even though there's still no fix
for the illegal instruction issue with 32-bit mariadb. But there should be
soon (thanks ponce!) No build regressions noted with the official gcc-10.3
release. Please report any new (or old) issues on the LQ Slackware forum.
Enjoy! :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.