[Pkg-kde-extras] KDE 4 apps.

[Mark Purcell]

On Wednesday 28 March 2007 09:08, Tom Albers wrote:
> > I assume that depends on the plans for the KDE 4 kde<whatever> packages.
> 
> Thanks for answering. The plan for Mailody is for example:
> 1st April Mailody 0.5 KDE3 based.
> 1st May Mailody 0.??-alfa1 KDE4 based, Mailody will release at the same times KDE releases alfa, beta's & rc's.

I doubt that Debian will switch to KDE4 in one quick change, that said hopefully there will be some sort of library
transition so we can have a smooth application transition.

1st April release of Mailody 0.5 we can upload quickly to unstable and then (hopefully) etch has released
and thus mailody 0.5 will transition to testing within the standard 10 days.

I doubt that KDE4 alpha/ beta/ rc will be released to unstable, I would imagine the team will wait until the
first real release to bring KDE4 to unstable.  Once KDE4 is released to unstable then mailody can also be
brought to unstable and I would imagine for a while we would have the KDE3 base and applications in testing
and KDE4 base and applications in unstable. Once the library transition/ applications are in a fit state I would
image that KDE4 base and applications would transition to testing around the same time.

Based on past experience the team may release KDE4 alpha (unlikely) / beta / rc to the Debian experimental distribution,
if this happens then we can use experimental as a bit of a sandbox for integration of applications into KDE4.  Then
once KDE4 releases we can move to unstable.

The question over releases to experimental seems to be mainly driven by available manpower and technical ability to
work with the fast changing upstream releases and issues.  Certainly it will easy the integration of KDE4 into Debian, but
it maynot be suitable.

> Ok, can we arrange things so it won't end up in the NEW queue for a month? Any convention about naming? 
> So it's clear for the user what's KDE4 based and KDE3 based? 

NEW being backed up for a month is actually a rare activity.  I suspect the problem at the moment is due to the
'imminent' release of etch taking longer than expected and the release team are other wise distracted rather than
processing NEW.

That said if you want to enable the KDE3 & KDE4 versions of mailody to coexist on the same machine
at the same time we would need to do something like have a mailody & mailody4 packages, which would have to go though new.

If we just have mailody 0.5 with KDE3 dependancies and mailody 0.6 with KDE4 dependancies, then the user gets the
libraries with whichever version they wish to install.  And dependanices will ensure that other applications/ libs are
conflict managed and removed.

> No responses or am I not on that list?

Looks like no response.

But that is where the manpower is coming from for the KDE3/KDE4 transition.

http://lists.alioth.debian.org/pipermail/pkg-kde-talk/

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20070328/46e295e5/attachment.pgp