Am Thursday 01 October 2009 schrieb Miklos Vajna:
> On Wed, Sep 30, 2009 at 12:46:52AM +0200, Daniel Exner <[email protected]>
wrote:
> > /me is proud to announce a (somewhat) dependency bug free kde431 WIP
> > repo. :)
> >
> > Now its time for intensive testing:
>
> What should we test? I mean should we test kde-extra as well, or you
> plan to fix that up later? Packages like 'baghira' have to be handled
> somehow, do you want to just remove them or you want to fix them / find
> replacement packages for them?
Some packages from kde-extra are already ported, some are deprecated since
their funcionality is included somwhere else (like kerry or katapult) and for
some (like baghira ) I have no plan (yet).
But my goal before merge to current is to handle the usecase
"pacman -S kde kde-extra"
in such a way to _not_ install software that can't work in kde4 :)
My TODO list for wip repo in descending priority:
1. Fix update of kde group
1.1 Split kdenetwork (at least kopete)
1.2 Split kdeutils (at least superkaramba)
2. Replace kerry
2.1 Fix nepomuk
2.2 Split it
3. Replace katapult
3.1 Split krunner (if possible)
4. Fix amarok
4.1 Fix qtscriptgenerator
4.1.1. Fix conflict between libqtxml, libqtxmlpattern
5. Check if its possible to use akonadi without mysqld (guess not)
6. Check why its not possible to install own splash screens (think path bug)
7. Replace as much as possible or at least deprecate it
Back to the question: you should first of all test if you can update to kde 431
from kde 3.5 (after uninstalling kopete and superkaramba) and if (most)
things work as exspected. :)
Greetings
Daniel "DeX" Exner
_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel
