Newer than Wheezy Korganizer?

[Mihai Badici]

On Tuesday, January 15, 2013 01:57:33 PM Jeroen van Meeuwen wrote:
> On 2013-01-03 14:19, Mihai Badici wrote:
> > At the moment those packages are rather
> > unknown and rather betas,
> 
> I'm afraid that's simply not true. We actively ship and support
> libkolab and libkolabxml for one of those other distributions frequently
> used on a workstation, and all we would need in order to include those
> packages in Debian itself (and therefore Ubuntu as well, but they have
> versions of these packages already) is somebody that is willing and able
> to go through the sponsorship process and become a Debian developer /
> package maintainer.

> 
> > so the sane option will be not to include them in
> > the distribution package.
> 

Sorry if you fill offended, whasn't my intention.
It's not about libkolab and libkolabxml, it's about the way those packages are 
integrated in Akonadi.

When a package maintainer will start compiling kdepim-runtime, will notice " 
there are no libkolab installed, kolab support will be disabled".

I think there are 90% chances to ignore this message and continue :) except he 
is a big kolab fan.

It's not realy a problem to compile libkolabxml, but usually I will prefer to 
use stock kde. And it's not about me, I think it will be better for regular 
users if kolab support will be included in stock kde.
But if somebody want to include kolab support, he must accept also two new 
packages in the main distribution. This is often a decision  must be taken at 
supperior level.

If kolab support is not in stock kde, there is just another package to 
maintain - kdepim-runtime ( by who?).

I'm sure it's technically feasable to include some kolab headers in main 
kdapim-runtime just to allow to compile with kolab support but whithout need 
to have libkolab installed. 


> If somebody is willing and able to build client packages for the Debian
> distributions that are not so much outdated, I welcome them to give it a
> go - I can offer a mirror, APT repository, a build system and the bunch
> of APT packaging git repositories for the exercise.
> 
> One could use these to attempt building the packages for the current
> distributions, and then aim to have the work be included with upstream
> for Debian Sid, for example.
> 
> Kind regards,
> 
> Jeroen van Meeuwen
-- 
Mihai Badici
http://mihai.badici.ro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20130115/05faa6af/attachment.html>