What features/changes would you like to see in future Slackware?
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.
One of the reasons to backlist a package is that there is a better one installed. For example, on my machine this happened to mc, ruby, freetype, and jre. Another reason is that one may prevent some packages from upgrading themselves unnoticed, like the kernel.
In both cases the default slackpkg behavior is suboptimal: it does not upgrade packages as requested, but gives no sign that the upgrade is possible. This requires extra effort to check for upgrades to blacklisted packages.
I guess there should be a configuration option to include blacklisted packages into upgrade-all and install-new when the dialogs are on and packages are selected by default. In this case blacklisted packages should be unselected.
Thus, it will be immediately evident that, say, it is time to upgrade the jdk since the new jre is there or that there is new kernel ready.
It's the users that are unstable. Watch the sh1t fly when the next version of Slackware is released without KDE3.
How ridiculous was the "debate" about the flippy logo...
I don't understand why people would be upset if Slackware 13 were to be released with KDE4 instead of 3.5.
XFce and Fluxbox, for having tried them both with Slackware, are other good choices. I've only recently come back to KDE after thinking that I hated it for years. OK, it'll never be a love affair between me and KDE, but it's no big deal. Linux is all about freedom of choice.
Besides, for you all you tech savvy and clever people this should not even be an issue. IMHO.
cheers!
I guess there should be a configuration option to include blacklisted packages into upgrade-all and install-new when the dialogs are on and packages are selected by default. In this case blacklisted packages should be unselected.
Thus, it will be immediately evident that, say, it is time to upgrade the jdk since the new jre is there or that there is new kernel ready.
I would like a "manual" configuration option, that works like you discribed.
I wouldn't want to have it in the blacklist. Some packages are blacklisted because they never should be updated, and I wouldn't want to risk upgrading aaa_elflibs because I accidentally selected the wrong package.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
A Live CD would be a good way of introducing more people to Slackware.
A friend recently installed Slackware 12.2 to a secondary drive in his otherwise windows box and what seemed to impress him more than anything else was the number applications that come with Slackware and that they ran, "out of the box."
If more people could simply run a Live CD and see what Slackware has to offer, without having to do an actual install, maybe we might have more
"converts"?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by dora
I don't understand why people would be upset if Slackware 13 were to be released with KDE4 instead of 3.5.
Quote:
Originally Posted by rkelsen
Me neither, but a simple search on "KDE4" in the Slackware forum will reveal some pretty strong (and mostly inaccurate) opinions.
Well, I can tell you why.
First, "mostly inaccurate" is purely subjective on your part.
I cannot believe that if you use KDE 3.5.10 daily either on your home computer or in a "there is work to be done" business environment you can say that 4.x is anywhere near as functional or configurable as 3.5.10. And, that I do not believe to be a subjective opinion.
I'm repeating myself, but I used KDE 4.x over a 6 months period, starting with 4.1.3, to 4.1.4, to 4.2, to 4.2.1, and finally, 4.2.2.
While it is attractive, very attractive, it is still missing many of the options you have with 3.5.10, that make it easier to get things done.
Perhaps, I should start writing down all the little things that are better, i.e, useful about 3.5.10, but in the two weeks since I did a fresh install of Slackware 12.2 and KDE 3.5.10 it has become very obvious to me that KDE 4.x is still not ready. Oh, you can get things done, true, but why give up what really works, on the promise that the "prettier girl" (kde 4.x) will someday learn to dance?
The trouble is I need a dancing partner now, not someday in the future.
Let's say, while 4.x is very pretty, she spends entirely too much time looking at herself in the mirror and has yet to fully develop a personality. OTOH, while 3.5.10 is not as "pretty" she can dance, cook, hold a conversation, and has an all around better personality.
Last edited by cwizardone; 04-26-2009 at 12:10 AM.
Reason: Typo.
Let's say, while 4.x is very pretty, she spends entirely too much time looking at herself in the mirror and has yet to fully develop a personality. OTOH, while 3.5.10 is not as "pretty" she can dance, cook, hold a conversation, and has an all around better personality.
You may be right. I liked KDE4 very much but finally switched to XFCE which also got prettier with version 4.6. I left KDE4 when I noticed that I am actually doing nothing and memory consumption is about 1 gig.
However, if Slackware 13 (is it known that it will be 13, not 12.3?) still ships with KDE 3.5, I guess QT 4 should be official and the default QT. Most 3-d party QT programs have switched to QT4.
However, if Slackware 13 (is it known that it will be 13, not 12.3?) still ships with KDE 3.5, <snip>
My money is on 12.3!
The naming convention seems to indicate a 12.3 in the changelogs but that could be changed on release. It's entirely up to PV for the decision if a Major or minor release number is used for Slackware.
The naming convention seems to indicate a 12.3 in the changelogs but that could be changed on release. It's entirely up to PV for the decision if a Major or minor release number is used for Slackware.
Yes. I am also curious as to how PV will name the next stable release. He has used 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, 12.2. Yeah, maybe he won't opt for 13. I think that 12.3 or 13 are likely version numbers.
How about Darkstar? I'm kidding, I doubt he'll move to using names.
I've heard it's going to be "Avaricious Aardvaark".
Brazen Buffalo?
To get back on track. If KDE4 is released with the next stable version I would like it to be optimized for speed and as bug free as possible.
The brand Slackware = stability.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.