Slashdot Mirror
KDE 1.1.1 is out
Well, the title says all - a new version of KDE is out with many bugs fixed,
better stability, and imporved internet connectivity. Here is the press release and the changelog
. You can download the files here (people with Redhat 6.0 Please check this doc). I hope that Linuxberg will have those files really quick.
The style of the press release makes me feel (unfairly) negative towards the product.
If they want to sound self mocking they need to strengthen it a bit ("the most significant development since the dawn of civilization" would be better).
I think I'm so used to this stuff from big business that I tend to tune it out and just feel slightly nauseous, but when you're not expecting it (as in this case) it's quite sickening.
Please send me instruction how to produce the
required packages.gz.
Regards,
--martin
Hi,
Does anybody know if they have fixed the following
problems which a lot of folks experienced with
kde 1.1?
1) When kfm is used, X keeps taking up more and
more RAM until all of it is used up, the system
then starts swapping and everything slows down
to molasses.
2) On at least some systems, KFM filemanager is
really slow, even slower than script-based
filemanagers like tkdesk.
3) It appears that kfm does not have access to
a lot of the fonts that are available. For example, on my system, it accesses only 2
`fixed' fonts. Furthermore, it keeps breaking
even short filenames into two or more lines,
which makes the whole thing look ugly. I'm sure
that I have used the Kfontmanager correctly to
make the fonts available to KDE, so that is not
the problem.
I have seen these problems mentioned in
newsgroups/mailing lists by other users, but
have not seen any fixes posted yet. If anyone
knows how to work around these bugs, I would
appreciate it.
Thanks,
Hari.
mailto:gharikumar@iname.com
Nice to see the debian packages in there, but could they include a Packages.gz and structure the directory (even sym link it) so that I can add a line in my apt/sources.list. - Any way keep up the great work KDE team.
KDE is one of the largest, most active and most successful open source projects. We owe a lot to those guys (any gals?).
There is tentative talk about GNOME compatibility/convergence, which is excellent.
Interesting thing about KDE is that it is now entering uncharted waters - the "chasing taillights" days are past them and the team is now doing new, innovative things, which tends to be the exception with open source projects.
I've lurked on the KDE mailing lists for some time. The development team is quite upset about the bad rap they get at slashdot and other such forums. This is really unfortunate. These are great people quietly doing great things. Be generous, hey?
Hi
o n/rpm
I ( duncan@kde.org) *AM* the packager of the KDE-1.1.1 RPM Packages for RedHat 4.2, 5.0. 5.1., 5.2 systems, that are currently available for your enjoyment at :
ftp://ftp.kde.org/pub/kde/stable/1.1.1/distributi
These packages are in the series produced by the independent (NOT RedHat-affiliated) redhat-rpm section of the KDE Packagers during the long period when Red Hat felt that KDE was not suitable for their distribution.
We aimed to provide a simple clean installation of KDE on top of a standard RedHat 4.2, 5.0, 5.2,and 5.2 system, and still support theses systems.
Our goal was to give the user an installation that did all the configuration necessary, with the minimum modification of RedHat's own setup. Judging by user feedback, and reviews contrasting KDE's installation (on RedHat) to that of e.g., gnome-1.0, I think we at least partly succeded.
KDE-1.1.1 is a "minor" (bugfix) release cleaning up little things that weren't quite right in KDE-1.1, but will be the "stable" desktop for the next 8-12 months while KDE-2.0 (with Corba, Koffice. qt-2.0, etc) is in development. Its release is significant as this will be the stable face of KDE for quite a while (there may be one more minor KDE-1.2 bugfix release at some point), but basically the developers have left 1.x for 2.0 development.
As far as RedHat 6.0 KDE support is concerned, they have in principle joined the ranks of Suse, Caldera, DLD, Mandrake, etc who package and support KDE themselves. (Well, not quite, as these others make KDE the default desktop) This takes the responsibility for RH6.0 KDE support out of the hands of the KDE Packagers Team.
We will continue to support RedHat 5.2, 5.1, 5.0 (and, if anyone requests it, 4.2), as RedHat will only handle KDE support on 6.0 and later.
I am sure they will do their best to make the KDE experience on RedHat 6.0 as easy as the one we have tried to give users on RedHat 5.x, and hope their packaging will allow the replacement of Gnome by KDE simple for those of us who wish to exercise freedom of choice to do this.
However, RedHat 6.0 rpm packages do *NOT* follow the packaging scheme I introduced with the KDE-1.1 release, where the optional KDE applications are all separated into individual RPM subpackages, so the user has complete control over exactly which optional KDE components are installed.
The RedHat 6.0 packages follow the "traditional" KDE packaging scheme of 10 collections of applications, where if a collection is installed, you get all its members. My understanding is that RedHat wanted to keep the KDE packaging more analogous to the way gnome was packaged. (A "level playing field"?)
The advisory from the kde ftp site quoted here is for people with KDE on RedHat 5.x systems who wish to upgrade to RedHat 6.0. Since I do not know whether RedHat 6.0 KDE packages "know about" the structure of our RedHat 5.x packages, we are advising people with upgrade from 5.x to 6.0 to use our "uninstall-kde" script to remove our packages first. This will *NOT* remove any of their personal KDE settings.
RedHat 6.0 ships with "almost" the final KDE-1.1.1 release; If you want a true KDE-1.1.1 release for RedHat 6.0, you must wait for RedHat to provide it, but the only differences will be very minor
Hmmm, this posting got rather long-winded!
Thanks for your patience!
Qt 2.0 will be released under the QPL 1.0 which is a DFSG-free / Open Source license. ( development snapshots are already available licensed under the QPL)
The QPL 1.0 is however incompatible with the GPL (Debian's analysis still holds for QPL 1.0). Thus, to redistribute binaries, an exception clause is needed like pi-address has:
The KDE developers are reportedly preparing a different license change that will resolve this conflict.
I'm afraid you'll have to stay hungry tonight troll as I won't be feeding you.
Perhaps you could go somewhere else?
Dramatic version updates.... like jumping from 0.30 over night to 0.90, quickly followed by a few 0.9.x (all of which made their way to slashdot) and then a premature 1.0 that hung ALL OF THE TIME while segfaulting and core dumping?
/. whinners would be complaining about how they aren't releasing anything new.
Why is it that KDE gets no respect? It's stable, it's fast, it works well. If they had NOT released a 1.1.x, than all of the
I wish people could appreciate KDE for what they have accomplished.
Hey, give them a break.
A lot of Linux folks are learning that while being technically better is great, you've got to play marketing games as well if you want your GUI, tool, what have you, to be seen.
KDE didn't call it KDE 2000 or 2.0, it was a first announcement, made its point and that was that. Were that all press releases so down to earth!
Steven, Senior Technology Editor, Sm@rt Reseller
No one is forcing you to upgrade. Do you upgrade your Linux kernel everytime a new version comes out? Judging from your post, I'd say that you probably don't. There is no need to upgrade your kernel everytime a new release comes out, unless it fixes something that you have had problems with. If you are not having any problems with your KDE software, then there is no need for you to upgrade. If, on the other hand, there have been fixes that would benefit you, then you should upgrade.
It is all about choice, you have the choice to upgrade if you need to. With many other systems (such as Winblows) you do not have that choice. You are at the mercy of the company that sells the product to come out with a fix (called upgrade) for problems (sometimes very serious problems) with the product. Sometimes you may have to wait months, or even years for these fixes. I, for one, prefer the way that many Open Source projects work... release quickly and release often!
---
Wow! Such as song and dance about a 1.1.X release! Haven't those KDE guys taken any lessons for the Mircosoft marketing team?
If you're trying to get a mass market for your product, improved stability and bug fixes would have been enough to warrant KDE 2.0!
Hmmm, to retain the respect of the development community and take over the world at the same time? I don't know if this is possible in today's market! Maybe you guys should turn a blind eye and let KDE slip in a few dramatic version updates every now and then to impress the punters...
BLAMMO shaken not stirred
Thats the first thing I checked and it does support cookies, still no Javascript though
PDG--"I don't like the Prozac, the Prozac likes me"
"Where is my mind?"