[gentoo-amd64] Re: kdebase-3.80.1

[Duncan]

"Richard Fish" <bigfish@××××××××××.org> posted
7573e9640608201150m3dd4d1b9md6dabdf3fe5683fd@××××××××××.com, excerpted
below, on  Sun, 20 Aug 2006 11:50:36 -0700:

> KDE just released the first developer snapshot of KDE4 and the
> announcement [1] makes it clear that there isn't much for end-users to
> see or test yet.  Generally the ebuilds for new KDE versions show up
> shortly after the first alpha release, and the KDE devs haven't given
> any dates for the first alpha, first beta, or final releases [2].  So
> I would keep an eye on [2] to see when there might be something useful
> to test.
>
> [1] http://dot.kde.org/1155935483/
> [2] http://developer.kde.org/development-versions/kde-4.0-release-plan.html

I'll second that.  I'm usually pretty out front, testing new things like
gcc, xorg, and kde, well before they are unmasked for even ~arch. 
However, the freshly announced KDE isn't anything I'll be installing yet. 
It's code-named "Krash" for a reason.  They've been pretty specific about
the fact that it has few new features for the end user, and is out there
almost exclusively for those developers that need something on which to
begin developing their own KDE 4 applications.  Not only is there little
if anything actually new (besides the fact that it's now running on Qt 4
instead of Qt 3), but it's /expected/ to crash frequently, thus the name. 
As long as it stays up long enough to be able to test whatever application
the developer is working on, say 10 minutes at a time, that's considered
good enough for now.

I too am looking forward to something to test, but the fact is, this isn't
an end user test version at all.  Running it now as an end user simply
isn't going to be all that useful, even for finding and filing bugs,
because they know about enough bugs at this time to keep them busy as it
is.  Again, this thing is known to be buggy, expected to crash frequently,
and is only out there at all in ordered to provide developers something to
work on to start upgrading their own non-core KDE apps.

As such, I'd be surprised to see it in portage at all.  I know I wouldn't
bother creating ebuilds for it at this point.  It'd simply create a stack
of useless bug reports, because the final product is going to be so much
different it will change out from under the current ebuilds anyway.

Thus, if you are /still/ interested in running it after all that, say you
ARE a developer for some non-core KDE application, you should expect to
build it directly from KDE, outside of portage, and as a developer, you'll
already know how and probably be doing it already.

JMHO, FWIW.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@g.o mailing list