Linked by Thom Holwerda on Thu 2nd Jul 2009 11:38 UTC, submitted by Witek Wasilewski
Slackware 13.0 RC1 has been released. Or tagged. Or whatever you'd call it in the Slackware world. "The TODO isn't entirely empty here, but it's pretty much down to minor nits, and so we're going to call this release candidate #1 and (mostly) freeze further updates unless they happen to fix problems. Regarding the kernel, 2.6.29.x has been well tested with this userspace and seems like the best choice to ship for production use. Perhaps we can put something else (at least source and configs) in /testing, though."
Thread beginning with comment 371505
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2009-07-03
Member since:2008-10-09
Used xfce.org dependency list as guide to compile the sources: http://www.xfce.org/documentation/requirements
Also created the slack build scripts to install the compiled modules as slack packages (for removal purposes if needed later). Browse in the slackware source directory to see the available SlackBuild scripts as samples and create your own based on them.
After the scripts are created just run them and the sources are compiled and packaged for installation.
Actually only special thing about those scripts are the fact that 'make install' is called with destdir parameter to install the module to specific directory and them slackware package is created by compressing that directory.
Edited 2009-07-03 16:35 UTC
Member since:2006-12-05
In Slackware, there is no such thing as default window manager. In fact you may choose not to install any window managers at all. All installation is text-based and one of the last questions it asks is what window manager the user prefers. Later this can be changed with xwmconfig.
Maybe I should clarify myself. By "default," I meant that Slackware, if you choose KDE, now uses KDE4 instead of KDE3. Xfce is good, and if it comes down to it I might just end up using that if I move back to Slack. I just have some serious doubts of KDE4 running well at all on my machine.
I for example installed slack 12.2 without any WM then compiled my own XFCE 4.6.0 (Slack 12.2 had 4.4) and used that.
I've tried compiling various small programs; some worked, and some didn't, usually because of dependencies. The last thing I would want to do is compile an entire desktop environment. In fact, the last time I did it was actually Xfce, with their fancy GUI "installer" and all. Even after installing a bunch of dependencies, I got nowhere. What fun.
Slack is too modular to complain about resource hogging.
Agreed, but assuming a typical user is used to running KDE3 in Slackware... it seems that either they're going to have to pack their bags and switch window managers, or hope they've got the resources to run its successor.
Member since:
2008-10-09
In Slackware, there is no such thing as default window manager. In fact you may choose not to install any window managers at all. All installation is text-based and one of the last questions it asks is what window manager the user prefers. Later this can be changed with xwmconfig.
I for example installed slack 12.2 without any WM then compiled my own XFCE 4.6.0 (Slack 12.2 had 4.4) and used that.
Slack is too modular to complain about resource hogging.