How much do you really know about all of the various distributions that
have KDE as their desktop default? With the flexibility of KDE and our
applications, distributions are able to focus on different goals, target
different users, and develop different personalities. Every couple of weeks, KDE Dot News will interview a distro maintainer to discuss the history of their distribution, what they are focusing on now and what their goals are in the future. To begin with we talk to Tomas Matejicek, the
founder and maintainer of SLAX,
a LiveCD based from Slackware.
The primary goal of SLAX is "to provide a wide collection of useful
software while keeping the CD image small enough to be written to a
185MB CD medium (small 8cm CD). SLAX boots directly from the CD or
USB devices and it provides a full featured Linux operating system." You
can learn more about SLAX on their features page and
download one of its versions and modules on their download page.
Can you tell us about the history of your distribution?
SLAX started back in 2002. It was just a test to make Slackware Linux
run from CD, but when several people found it useful then I decided to
start the project.
Why did you choose KDE and which version of KDE did you first implement?
I chose KDE because Slackware installs KDE into /opt so it was
very easy to distinguish KDE files and the rest of the system. Moreover
I like the look of KDE, in my opinion it has the best icons
available. The version of KDE was 3.1.
How did you find initial support for a new distro?
I didn't find any. I tried sourceforge.net, but they refused to provide
web space for SLAX. I had to setup my own server and pay for it.
What could KDE have done better to help new distros use KDE?
I would suggest a better packaging system. For example, when I wish to
install KWord, I must install all the rest of the KOffice package. This
is usually not any problem for end user, but for distro packagers it's
important. Nobody wants useless files.
What were your first impressions about KDE's documentation and community?
It's huge! :)
How closely do your releases depend on KDE releases?
In the past, it has been very close. Nowadays it doesn't depend on it,
but it's always nice to have the latest version of KDE in SLAX, of course.
Do you have a clear target audience for your distro?
All users who need very small system with KDE.
Do you have any user feedback mechanism? If so, what feedback do they have about KDE?
Yes, users talk to me personally by email, or by using our web-based forum.
They say only good things about KDE, they like it because it looks so
good. Moreover I choose only KDE applications for SLAX so the whole
desktop seems very coherent, all apps look the same. Users like it, of course there are still some people who suggest FluxBox :)
In what ways do you customise the version of KDE that ships with your distro?
I'm using Slackware's packages only for Arts, Qt, KDEBase and KDELibs.
The rest is recompiled because I want to include only some
applications, not the whole packages. For example, I include KWord,
KSpread and KPresenter in SLAX but nothing else from the KOffice package.
What are the biggest strengths of KDE for your distro?
The design. The icons. The amount of applications shipped with KDE.
What are the biggest weaknesses?
The applications shipped with KDE :) As I said, it's hard to compile
KWord alone. This should be improved IMHO.
What KDE applications are the most popular among your users?
I don't know. SLAX uses only KDE applications as default so it's hard to
say. I think that Kopete is very important, KPlayer (mplayer frontend)
and K3b (burning software).
Do you feel that you have a good relationship with the KDE community?
I don't know. I don't talk with KDE people much. But KDE are
using SLAX as a base for the official KDE Live CD (Klax) and I like it :)
What feature would you as a distro maintainer like to see in KDE?
Easily customisable package building. Possibility to compile only one application from the package (again, the previously mentioned KWord, for example). Maybe this is already possible but I didn't find any documentation. The DONT_COMPILE variable doesn't work well for me.
Is the extended 4.0 release cycle an issue for your distro?
Not at all.
What are you most looking forward to about the 4.0 release?
Wobbly windows by using 2D acceleration (without 3D cards).
Do you plan any involvement in the beta/RC releases of the 4.0 release?
Sure I test every beta/RC, moreover sometimes I release KDE RC versions
with SLAX too.
Any other plans for your distro in the future?
Sure, a lot of plans, but not about KDE :)
Personally I have been using SLAX for few years now for rescuing systems as I tend to be kinda aggressively updating my system packages, and once in a while systems tend to break, and installing older RPM, re-merging and/or reconfiguring /etc files become pretty simple and fast to do with such LiveCD as SLAX.
Just too bad some of the systems I maintain have 64-bit systems on them, and as I can't chroot on them from 32-bit SLAX it leaves me no choise but to use other LiveCD for them (actually using RR64 LiveDVD for now)... So maybe there might some day me a SLAX64 (I bet this question resurfaces from time to time)?
And of course one other major usage has been going about booting SLAX to non-expecting "the other OS" user's computers (giving excuses like "I really can't use my WebMail from non-Linux system, heh). ;-)
What's he mean "wobbly windows"? Anybody got a URL?
he means in other words the upcoming versions of X.org that is X7.1 which technically speaking has already been released for several months, however only three or so distributions have implemented it. In other words he is looking forward to X7.2 to be released to the end of the year, in the same time window as KDE is slated, a tad bit before perhaps.
Ah what the heck see for yourself go to google - kororaa
Thi XGL is really fine. I'm using it daily and my CPU is less used and memory too, but I can't use Xorg 7.1 because nvidia binary drivers still aren't compatible with it.
According to Tomas, it seems the best thing about KDE is the look. I have to disagree about that...
we could just short circuit your comment quite easily with sth like:
really, it's not surprising there are people who dissent. for any given opinion. the real finesse is knowing when it matters a rat's ass to dissent publicly, which usually comes down to having an interesting reason for doing so. that can range from "huge numbers of people agree with me" to "i have an interesting insight".
but simple "i dissent"? *boring*
I am not sure I understand what you want, because on most distribution I have tryed, you can install kword (and most other kde apps) independentely, so I had say it's more a distribution problem than a kde problem.
I don't think you understood what he meant. Huge source packages like koffice-$VERSION.tar.gz makes difficult to create individual packages for the applications they contain, like kword. Sometimes, it would easier to have libkoffice-$VERSION.tar.gz and indivual source packages. Another example is how difficult it is to create a JuK binary package from the kdemultimedia source package.
Is it more undestandable ?
> Another example is how difficult it
> is to create a JuK binary package
> from the kdemultimedia source package.
It's easy if you use svn2dist.
I have to agree with Tomos. I find this the most annoying aspect of KDE. With each release, the download files of both KDE and Koffice get ever bigger, as the developers add ever more features/programs. If everyone used every feature/program, that wouldn't be a problem, but they don't, so in effect it's just so much bloat. It's particularly bad with the bugfix releases: only a small number of files have actually changed, yet you have to download the whole lot, even if you only use a small number of programs - this is horribly inefficient.
I look forward to an improved packaging system in KDE4!
As far as I'm concerned, you won't get it for KOffice. Packaging the source tarballs for a release is done by developers, not by packagers. Packagers then package the source into as many different installation packages as they want for the distribution they work for.
I, as a KOffice developer and release dude, simply don't have the time to split the KOffice source into a package for every application. Preparing a KOffice release already takes four full days: one for the tagging/packaging of the source, one for the tagging/packaging of the languages and two more for preparing the changelog, release notes, press release, coordinating with packagers, translators, news sites.
It may be inconvenient for you, but if you want to install from source, you might just as well install from a subversion checkout, and if you don't want to install from source, your distribution will provide separated packages for you. And if you're working for a distribution and want KOffice source packages delivered in separate packages (and have agreement from the other distributors that they want it that way too), you might volunteer to take over the source packaging process from the developers -- i.e, me.
Time is like money: it's hard to believe that someone else hasn't more to give.
As for a user, if he wants to select apps he should use a distribution that allows it. If he builds it, he can use kdesvn for that. (you are not force to use trunk or to download the source for all application)
As for packagers, well downloading one tarball or a dozen of tarball, I am not sure it will be a winning situation. And if you consider the amount of work needed to release KDE and/or KOffice and that is usually done by one person, I really doubt that is worth to split KDE in smaller package. And I also heard complaints from people about xorg being split in too much packages, personnaly, I do find KDE to be well balanced with thematic packages.
I didn't know about svn2dist, I'll definitely check it out!
What I meant by kword (or juk if you wish) is the following:
I wish to compile it from sources.
I wish to compile only kword/juk and all indispensable dependencies, nothing else.
For me (as a distribution packager) would be useful something like 'make juk' and 'make juk_install', for example.
The ability to only compile some part of the KDE packages has been there forever(Or at least since KDE2). You have to exclude the parts you don't want, just set DO_NOT_COMPILE="the ones you dont need".
This is not working as expected, or I don't understand how to use it correctly.
Slax is great. It is really good as a rescue kit and it allows me to use linux on my parent's computer (BTW I noticed Slax seemed faster there than their windows XP)
I was using ubuntu and after finding and trying out slax I had to switch to kubuntu. There is no better advertisement for KDE.
May be you have not seen Tomahawk Desktop :)
I like Slax, it is fast and useful. I missed Slax with KDE 3.5.x series. Could you please have next version of Slax with next version of KDE ;) thanks!
Hey! You forgot to complain about printing quality!
Slax has been one of my favorite livecds because it is fast and easy to customize. Some friends got fed up with "that other operating system" and asked me to install Linux. I installed Slax with extra applications (Slax modules) and created a livecd that was almost identical to what was installed on their desktop. No matter how bad they trash their system, they can boot to their custom livecd and have their familiar desktop and applications.
Tomas - keep up the good work.