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.
Because replies of this topic became generally offtop, I propose to rewrite a bit question:
What is cooking in Slackware's kitchen now?
I mean, is there any huge or little projects in testing by Pat & Co? If we shall know that will shall be able to assume more or less precisely when it could be done and so when next "ready" state can be achieved.
When this was asked in the "Current seems a bit slow" thread we had a while ago, Eric popped up and said there wasn't anything cooking and we shouldn't expect any big-bang of updates. That was part of what lead me to conclude that Pat was just taking it easy while he has the chance. (complete supposition on my part)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,087
Rep:
Quote:
Originally Posted by GazL
When this was asked in the "Current seems a bit slow" thread we had a while ago, Eric popped up and said there wasn't anything cooking and we shouldn't expect any big-bang of updates. That was part of what lead me to conclude that Pat was just taking it easy while he has the chance. (complete supposition on my part)
Ah, well... As I've said before, I once asked if there would ever be a 64 bit version of Slackware in the foreseeable future and was told a very firm, no. Two and half or three months later Slackware64 was announced and from the discussion that followed it was plain to see it had been "cooking" for many, many months. So, as the old sayings goes, "Once bitten, twice shy," or "First time, shame on you. Second time, shame on me."
Last edited by cwizardone; 12-01-2011 at 10:45 AM.
Ah, well... As I've said before, I once asked if there would ever be a 64 bit version of Slackware in the foreseeable future and was told a very firm, no. Two and half or three months later Slackware64 was announced and from the discussion that followed it was plain to see it had been "cooking" for many, many months. So, as the old sayings goes, "Once bitten, twice shy," or "First time, shame on you. Second time, shame on me."
Ah yes :-) I seem to recall that my usual answer would be a pertinent "Pat is not developing a 64-bit Slackware". Which was a true statement right up to the official announcement of Slackware64. All the while I had been its sole developer, keeping my hidden 64bit tree in sync with the official 32bit tree while I gradually built all of the packages. Of course, everyone with a keen eye could see it coming, because every SlackBuild I re-wrote (and I touched virtually every script) ended up in the public -current tree as soon as Pat updated a package.
So, since XFCE is coming to speed (4.8), and KDE is "koming" to bloat will we get back to Gnome (tight as ever) again?
I only use XFCE4.4 and fluxbox anyhow (KDE overbloated my non-gaming-hardware boxen )
Point being it is simple to run newer versions of things as long as you don't start messing with core system tools and libraries.
Or even if you do, sometimes. For example, I've rebuilt SDL with a Mercurial checkout of SDL_Mixer, which supports soundfonts. It was very easy to do so with Pat's SlackBuilds.
uhm... what's wrong with Slackware 13.37? It is working fine for me.
Slackware 13.37 is wonderful; I don't think anyone was being critical of 13.37. The next stable release of Slackware will arrive when it is ready. I predict that Slackware 14.0 (my prediction on the release number) will be stable, secure, and feature-rich. Some things never change.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.