kde4

[Sune Vuorela]

(this entire mail is my personal opinions and a proposal - and even if I sound 
like it is something decided, it is just my writing style ;-)

Hi!

KDE4 is coming - one day. Alphas are coming at May 3rd. I think we should try 
package the alphas.


BUILDING

We need a lot of things in order to make kde4 usable. Partly a new 
infrastructure is needed.

KDE4 uses cmake as build system. CDBS does not have anything directly that can 
help us - but there is a cmake.mk in some of the kde-exstras packages, that 
at least can serve as a inspiration.

The other parts of cdbs, the current kde.mk and the debian-qt-kde.mk does at 
least need to be looked very carefully thru, if not completely rewritten.

We also have the opportunity to skip cdbs if we feel like. Or move patch 
system to nice quilt. And other decisions. But I think we need the decisions 
now.

In general I would think we should start from scratch with empty debian dirs 
in all source packages and take it from there. Maybe keep changelog for 
historical purposes.


RELATED PACKAGES

kde4 currently uses a newer qt4 than the 4.3beta found in the kde subversion - 
no one knows when qt4.3 will be stable - so we need to get qt4 updated to the 
the snapshot at least.

strigi is a very important build-dependency of kdelibs. And a newer snapshot 
from kde trunk is also needed. I would also suggest moving strigi from 
pkg-kde-extras to pkg-kde. And integrate the maintainers to pkg-kde team.

dolphin is currently packaged in debian as a seperate thingy. Dolphin will be 
the file manager in kde4 so we need some cooperation.  I suggest 'hijack' the 
package and assimilate the dolphin maintainers to pkg-kde team.


KDE4 - PACKAGES

I would like if we could hook up with the 'review package descriptions' team 
to create some useful goot package descriptions.

I would also like if we aimed at making all the packages lintian clean. As 
everything needs to be reworked anyway, we have the opportunity to do it.


KDE3

I don't know fully have decided what to do about kde3 for the future. Maybe 
starting with a amputated kde3libs (skipping khtml and maybe other parts as 
well) to keep some compability and skip the rest of kde3. Maybe just skip 
entire kde3.
Most packages build-depending on kdebase-dev is window decorations - so that 
could easily go away. But really many packages uses kdelibs.


KUBUNTU

Closer cooperation with kubuntu about kde4 would be nice. I don't know if it 
should be thought into the build infrastructure.
kubuntu has packages out in the wild. I don't know if they could be used for 
inspiration.


TIMELINE

upstream timeline starts with a + 
My suggested actions are written in between - but maybe too tight.

+Mon, 30 April: Merge Phonon/Solid API cleanup branch.  Merge Nepomuk
+Tues,  1 May: Begin kdelibs soft API freeze
Have qt4 and strigi updated.
Review cmake.mk and decide on what to do about how to build
+Thu,  3 May: Tag KDE 4.0 Alpha1
Infrastructure somewhat usable.
Preliminary packages of kdelibs, kdepimlibs, kdebase ready
+Tues, 8 May: New Application Freeze, Start Usability and Accessibility Review
Do the rest of the packages.
+Mon, 14 May: Tag KDE 3.5.7
Do kde3.5.7.
+Tues, 22 May: Expected release date of KDE 3.5.7


Any comments - including "Are you completely insane" is welcome.

/Sune

-- 
I cannot log from the display from the control options inside Excel NT, how 
does it work?

You neither should rename the cable, nor can ever digit from a ethernet prompt 
of a LCD terminale on the fan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20070427/4c137568/attachment.pgp