On 04/04/06, Diego 'Flameeyes' Pettenò <[EMAIL PROTECTED]> wrote: > usable state-, KDE 3.5.1 was a bit better but stills some patches were > needed, KDE 3.5.2 is in portage since less than a month, and already had a > few patches with revbumps to few memleaks and crashes, a new kdelibs revbump > is also planned, and umbrello 3.5.2 is regressed compared to 3.5.1 (that > still, vanilla, wasn't usable for activity diagrams at all).
Surely the question isn't whether the upgrade is perfect, but whether it's better than the current stable release? 'find /usr/portage/kde-base -name '*3.4.3*.patch' |wc -l' shows 15 patches, 3.5.1 has 11 patches, and 3.5.2 has 6 patches. (I realise that isn't a perfect patch count...) >From the handbook: "The use of ~arch denotes an ebuild requires testing. The use of package.mask denotes that the application or library itself is deemed unstable." As far as I can see the *ebuilds* for kde work fine. If the newer versions of kde have the problems you describe, then they should be package.masked. I think at this point it does more harm than good to be lagging behind the current upstream kde - last time I checked the kde bugzilla wouldn't even accept bug reports for the kde currently marked stable as it was too old, and if bugs can't be filed then it's clearly "unsupported upstream" and time to upgrade. -- [email protected] mailing list
