Packaging effort...

Hi,

Same observation as Alexander in his "KDE wins" mail! ;-)
Now that things start to get going, it is time to make a great use of the 
available server... and it's package repository!

So, I tried to identify which packages would be useful, which one are already 
done, which one lacks, etc.

Here are my conclusions.

We need a bunch of metapackages for the different profiles we want to cover, 
as stated before by Alexander (goodness... you are everywhere! ;p), Liz Young 
started some work toward this goal. Liz, are you still around? It's time that 
your kalyxo-office package goes into our workstation-unstable branch...
Please contact me privately if you need informations to put it in... I'll help 
you as much as I can.

Moreover, we need some packages not available in debian now. Some of them are 
already available in our repository... some aren't, so they should be our 
primary target.

------- 1) Packages available on our repository ------- 
gtk-qt-engine (packaged by Christoffer Sawicki)
kapture (packaged by Peter Rockai)
knetworkconf (packaged by Christoffer Sawicki)
luma (packaged by Peter Rockai)

------- 2) Packages not available but in progress ------- 

fuse_kio (work in progress by Peter Rockai)

pykde (work in progress by Ricardo Javier Cardenes Medina, the debian packager 
of pyqt), IMHO this one is really crucial since some of our work is done 
using python... Please note that it'll be subject to further investigation, 
as the situastion is somewhat confused (the fact that it's not inside  
kdebindings doesn't help here)

kdebindings (work in progress by Dominique Devriese)

------- 3) Packages not available and no work in progress -------
cuckooo (see kde.openoffice.org)
KDE NWF (see kde.openoffice.org)
libgtgtk
guidance (Simon Edward's tools)


If somebody wants to add a package to this list, please let us know. As soon 
as we have a wiki (or something else appropriated) on kalyxo.org, I'll put 
this online. It will help us to coordinate and avoir effort duplication.

In my opinion, our policy should be to have our package available as soon as 
possible in our repository, and then take the time to migrate them in debian.
This migration will be only possible thanks to the debian developers involved 
in Kalyxo. They'll be able to sponsor/proxy our Kalyxo package into Debian.

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."