Linked by Robert C. Dowdy on Tue 8th Oct 2002 02:36 UTC
Red Hat I know what you're thinking, but don't worry. This article isn't 'Yet Another Red Hat 8.0 Review'. This article is primarily about using Red Hat 8.0 if you happen to be a newbie, but it's also about using Red Hat 8.0 if you happen to be a KDE user. Why? I happen to be a KDE user, so it makes sense I'd focus more on what I know the most about. Plus, I still remember the frustration of staring with something akin to terror at a blank command line with lots of ideas about what I'd like to do and very little knowledge of how to do it.
Permalink for comment
To read all comments associated with this story, please click here.
...
by rajan r on Wed 9th Oct 2002 07:13 UTC

Chris: Does this mean that Macromedia is making Flash for Linux, or is he talking about a plugin?

Obviously the plugin. The editor is called Flash MX.

Mongre: The issue that the KDE group has with RedHat is not that RedHat is making KDE look different, but rather applying incompatible broken patches and not contributing them back to the core KDE team.

Amazing to note that most KDE developers, if not all, actually bitching about this never once used Red Hat 8.0 nor its betas. Besides, the fact that Red Hat never contribute the patches back to KDE is because many of these patches is vendor/distribution-specific, and wouldn't be accepted by KDE. Other patches that aren't distribution-specific already have its altenatives in the CVS, heading for either 3.1 or 3.2 releases. (And I noticed, nobody bitched about Xandros or Lycoris or Lindows changes not going back to KDE...)

Mongre: The problem stems from RedHat either failing to understand, or ignoring the fact that KDE is amazing customizable without even touching code. They do not need to break the libraries to get their "branding".

Ahhh, the usual. Now, for an example, tell me how do you place XFT2 as the font renderer without any changes to the code?

Mongre: What you have is traditional gnome teams making incompatible changes to core KDE libs and trying to hide the controversy they created by blaming marketing for the need to "brand" the desktop.

What makes you think it is GNOME developers changing KDE? Ahhh, pure FUD. Love this season.

Mongre: One thing you did not mention that of them all only RedHat is not submitting their patches to the KDE group.

Red Hat is a keen supporter of GNOME, yet they didn't contributed back the bulk of the patches into GNOME. Nooooooo.... they didn't. Besides, these distributions have little by little turn their focus away from the desktop, and the smaller ones supporting Linux (including Lindows.com. a KDE League supporter) don't give back their patches to KDE.

Think about that.

Mongre: I am sorry but the fact is your are defending a company who is perhaps for the first time in its history violating the spirit of Open Source. The spirit of cooperation.

Hehe, by you standards, they have violated the so-called spirit of OSS (remember 7.0 with the broken GCC?) many times. I'm sure Red Hat is willing to co-operate with KDE< but KDE developers have been very cold towards Red Hat in general. They expect Red Hat to support KDE as much as they do with GNOME....

Xenos: Their "display" gui tools won't let me set 32-bit colors! Only 16 or 24, and I don't have 24.

In X11, 24bit=32bit. 32bit only adds alpha transperancy, which X11 by default doesn't support.

Xenos: Andrew: You miss read my point. I know what the difference between 24-bit & 32-bit color. My video cards does *support* 24-bit color, only 32.

Firstly, I think you meant doesn't instead of does. Here am I running RH 8.0 under 24-bit colour mode, while the GPU documentation says 16-bit or 32-bit. Try it out first, if it doesn't work, fill in a bug report.

Xenos: Linux_baby: I have one of those printers that works with only cups.

Which is? (brand name and model)

raul pitti: why not port a clean kde to RH8.0

It is entirely possible to run vanilla KDE without any changes on Red Hat, not need to port.