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.
It looks like KDE 4.3.4 may be the last 4.3 bug fix release as KDE 4.4 is coming soon.
I'm wondering if there is any plan yet for a Slackware 13.1 release and if that might occur shortly after the last 4.3 bug fix release. I don't know if KDE 4.3.4 IS the last 4.3 bug fix release but it might be.
Because of the issues in KDE 4.2.4 and the fact that KDE 4.3.3 seems to be more stable and a bit faster, I'm wondering if the next Slackware release might come sooner than usual.
It's hard for me to tell how much better KDE 4.3 is than KDE 4.2 since I had problems with both versions. I'm using KDE 4.2.4 since that was officially released with Slackware 13. Actually I'm mostly using XFCE4 now with some of the KDE applications.
Well considering KDE4.3.3 is in -current, we can expect 4.3.4 sometimes in the future. There is no question of 13.1 being out so soon, 13 was just released a while back. I think 4.3.4 maybe included in 13.1 if it's stable enough. I doubt whether 4.4 will be included as it will mean a lot of changes, like qt 4.6.
Also, I believe 4.3.4 is the last maintenance release since 4.4 is supposed to be out by Feb2010.
The way that Slackware is contained. Right now we have order copies that are dual sided. We have download mirrors for a particular arch. Slackware doesn't have a LiveCD unless you consider the Install CD/DVD as one. Sure there's 'Slax' but with today's technology we have media choices that could be used for a Live distribution. So to be productive and available a repackage would be nice.
Please don't take my statement as being anti-Slackware. It's that loads of people in the GNU/Linux community look down at Slack as it's still not GUI based install. Sure, the curses works for me and I prefer it but word of mouth sells big. I don't want a hold your hand distro and believe every method should be looked at to achieve a true community distribution. Most people just want their computer too work.
Stability and reliability are what counts so Slackware meets these requirements hands down without debate.
It's that loads of people in the GNU/Linux community look down at Slack as it's still not GUI based install.
Those people are better off not using slackware.
Slackware installer for me is perfect. Kind of like Arch, but more informative. You actually understand what's being installed and what the package does. Selection is simple as well. I wouldn't change a thing about slackware. That's just my opinion.
Yes, but we are familiar with Slackware installs and functionality. Slackware doesn't have to be a hold your hand distribution to have a GUI install. Plus having multiple choices for install media would be a big plus along with a boot selection for the method of install.
I don't want a hold your hand distro and believe every method should be look at to achieve a true community distribution. Most people just want their computer too work.
Stability and reliability are what counts so Slackware meets these requirements hands down without debate.
Agreed. For me Slackware is designed perfectly; I like being able to configure my system with a text editor and the CLI. Slackware's KISS philosophy works.
Stability and security are Slackware trademarks.
Yes, but we are familiar with Slackware installs and functionality. Slackware doesn't have to be a hold your hand distribution to have a GUI install. Plus having multiple choices for install media would be a big plus along with a boot selection for the method of install.
Yep I think that would be a great idea, like Debian has both GUI and Text based install. Use whichever you like. However, doesn't that go against the KISS philosophy?
I had the same thought that 13.1 may have a release interval on the short side of average, but I wouldn't expect it before March. I've never seen a release faster than 6 months, but I doubt this will be another 13-month wait like 11.0 was.
The timing of 12.2, the announcement of 13 RC1, and the KDE releases of 4.2.4 and 4.3 RC1 just didn't seem to line up well. Waiting on 4.3.0 could've pushed the release of 13 too far, so I can understand going with 4.2.4.
Pat & crew did get 4.3.2 into -current about 6 weeks after 13, and only about 2 weeks after KDE released it. That should satisfy most folks who really want 4.3.
Yep I think that would be a great idea, like Debian has both GUI and Text based install. Use whichever you like. However, doesn't that go against the KISS philosophy?
I think it's doable and still be a KISS. Text based is simple and reliable. But you need to remember that a lot is dependent on the user for this technique. Loads of people find it complex in a since for lack of transparency.
Now if you cookbook a recipe for a install you will still find people that don't follow directions be it because of communication barriers or just plain unable to step through properly. As some say; 'He couldn't pour piss out of a boot even if the instructions were on the bottom of the boot'.
Back on topic, KDE4.3.4 should be in 13.1 but 4.4 will require rebuilding apps with qt4.6, and since this is a version jump, a lot of new features will be introduced, testing could take a while.
Back on topic, KDE4.3.4 should be in 13.1 but 4.4 will require rebuilding apps with qt4.6, and since this is a version jump, a lot of new features will be introduced, testing could take a while.
I would be happy with KDE 4.3.4 in the next Slackware release if that proves to be a good enough KDE version. I've always been in favor of Slackware using the most stable and supportable versions of software rather than the latest versions. That does assume there is a stable version of something, and KDE still seems unfinished. I'll remain patiently eager for Slackware 13.1.
"We don't need no stinkin' graphical installer!" I like the Slackware installation disc just fine. It boots fast, then takes care of the most tedious and complicated part of the process (the packages and some configuration). I had no trouble at all following the text setup menus. Slackware does not have to try to be the most popular distro, nor imitate the other distros. The goals of Slackware are different. There are plenty of choices for live Linux discs and autopilot distros. The takeoff might be a little more bumpy with Slackware but it's so much better when I get to fly the plane instead of just being a passenger.
I just took the tree from slackware64-current/source/kde
put new source files to slackware64-current/source/kde/src
changed version in KDE.options to 4.3.4
and everything built as it should. I am running 4.3.4 for more than 1 day. And I donot really see any difference. Purhaps some bugs were fixed, but I do not see any difference as everyday user.
And there is no need to push for new release just because new kde bugfix was released. I believe, to get new release there should some major changes. For example new x server, which should be out next spring, I believe.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.