OpenSuSE 10.3 integration

I found the OpenSuSE 10.2 page (http://en.opensuse.org/K
olab), but I'd 
like to use 10.3 and divert from the tree as little as
possible.
Looking at the Wiki, the current SuSE Postfix package
(2.4.5) should not 
need patching?
It looks like the only place it diverges is with c-client,
cyrus imapd 
and PHP?
I'd want to stick with the current PHP 5.2 as well.
Hooking in with Horde is also important to me.  I am using
Horde IMP and 
the Contact/Calendar SyncML stuff right now.
How much work am I looking at?  Should I create some
packages and put 
them up somewhere?

Thanks,

Eric

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Hi Eric,

Eric K <eknuds-kolabknudstrup.org> writes:

> I found the OpenSuSE 10.2 page (http://en.opensuse.org/K
olab), but I'd 
> like to use 10.3 and divert from the tree as little as
possible.
> Looking at the Wiki, the current SuSE Postfix package
(2.4.5) should not 
> need patching?

Right, the postfix patches went in with postffix-2.4.0 so
there is no
patching needed.

> It looks like the only place it diverges is with
c-client, cyrus imapd 
> and PHP?

Exactly. All patches necessary for non-Kolab packages are
being kept here:

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patc
hes/

> I'd want to stick with the current PHP 5.2 as well.

No problem.

> Hooking in with Horde is also important to me.  I am
using Horde IMP and 
> the Contact/Calendar SyncML stuff right now.

The Horde patches are also in the directory given above. Are
you using
Horde with a Kolab server right now? I'd not expect SyncML
to work
with the Kolab drivers at the moment. The changes added to
the Horde
share system still pose some problems to the internal API
calls.

> How much work am I looking at? 

A lot. It took me about half a year to get the first
Kolab2/Gentoo
version that was clean enough to install for somebody other
than me to
install. It might be easier now but it is still far from
trivial. The
patching is not really a problem. I believe configuration
and
packaging are the main problems.

> Should I create some packages and put them up
somewhere?

I'd suggest to contact Richard Bos and Marcus Hüwe that are
responsible for the current Kolab2/OpenSuSE project. They
both know
Kolab extremely well and are of course integration experts
when it
comes to OpenSuSE. They were actually the ones that made
integration
of the Kolab server in other platforms possible without
extreme
hacking.

I guess they are also interested in OpenSuSE 10.3. So maybe
there is a
chance to collaborate.

Cheers,

Gunnar

>
> Thanks,
>
> Eric
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Gunnar Wrobel wrote:

> > Hi Eric,
> >
> > Eric K <eknuds-kolabknudstrup.org> writes:
> >   
> > Right, the postfix patches went in with
postffix-2.4.0 so there is no
> > patching needed.
> >   
>   
Great!

> > The Horde patches are also in the directory given
above. Are you using
> > Horde with a Kolab server right now? I'd not
expect SyncML to work
> > with the Kolab drivers at the moment. The changes
added to the Horde
> > share system still pose some problems to the
internal API calls.
> >   
>   
That's a bummer.  I wonder which would be more work. 
Getting another
front to work (such as Funambol) or updating the Horde
SyncML
implementation.
Right now I'm using Horde with the MySQL backend.

> > I guess they are also interested in OpenSuSE 10.3.
So maybe there is a
> > chance to collaborate.
> >   
> > Richard sent me a reply, so yeah, I'd like to
assist in the effort
> > somehow.
>   
I'm starting a new job in a couple of days so I may not have
an excess
of time and energy.
I think what I'd like to do at least is try to build a
verson of the
core Kolab package for 10.3 that doesn't need a separate
Postfix package.
My current server is completely functional but getting a
little out of
date, so I'm looking to do something soon.

Eric

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Hi Eric,

Eric K <eknuds-kolabknudstrup.org> writes:

> I found the OpenSuSE 10.2 page (http://en.opensuse.org/K
olab), but I'd 
> like to use 10.3 and divert from the tree as little as
possible.
> Looking at the Wiki, the current SuSE Postfix package
(2.4.5) should not 
> need patching?

Right, the postfix patches went in with postffix-2.4.0 so
there is no
patching needed.

> It looks like the only place it diverges is with
c-client, cyrus imapd 
> and PHP?

Exactly. All patches necessary for non-Kolab packages are
being kept here:

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patc
hes/

> I'd want to stick with the current PHP 5.2 as well.

No problem.

> Hooking in with Horde is also important to me.  I am
using Horde IMP and 
> the Contact/Calendar SyncML stuff right now.

The Horde patches are also in the directory given above. Are
you using
Horde with a Kolab server right now? I'd not expect SyncML
to work
with the Kolab drivers at the moment. The changes added to
the Horde
share system still pose some problems to the internal API
calls.

> How much work am I looking at? 

A lot. It took me about half a year to get the first
Kolab2/Gentoo
version that was clean enough to install for somebody other
than me to
install. It might be easier now but it is still far from
trivial. The
patching is not really a problem. I believe configuration
and
packaging are the main problems.

> Should I create some packages and put them up
somewhere?

I'd suggest to contact Richard Bos and Marcus Hüwe that are
responsible for the current Kolab2/OpenSuSE project. They
both know
Kolab extremely well and are of course integration experts
when it
comes to OpenSuSE. They were actually the ones that made
integration
of the Kolab server in other platforms possible without
extreme
hacking.

I guess they are also interested in OpenSuSE 10.3. So maybe
there is a
chance to collaborate.

Cheers,

Gunnar

>
> Thanks,
>
> Eric
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Op zondag 14 oktober 2007 08:42, schreef Eric K:
> > > The Horde patches are also in the directory
given above. Are you using
> > > Horde with a Kolab server right now? I'd not
expect SyncML to work
> > > with the Kolab drivers at the moment. The
changes added to the Horde
> > > share system still pose some problems to the
internal API calls.
> > >  
> >
> >  
>
> That's a bummer.  I wonder which would be more work.
 Getting another
> front to work (such as Funambol) or updating the Horde
SyncML
> implementation.

In the long term getting Horde SyncML work would be better. 
As this will 
provide 1 interface instead of this another to all people
using kolab in 
combination with horde.

> Right now I'm using Horde with the MySQL backend.
>
> > > I guess they are also interested in OpenSuSE
10.3. So maybe there is a
> > > chance to collaborate.
> > >  
> > > Richard sent me a reply, so yeah, I'd like to
assist in the effort
> > > somehow.
> >
> >  
>
> I'm starting a new job in a couple of days so I may not
have an excess
> of time and energy.
> I think what I'd like to do at least is try to build a
verson of the
> core Kolab package for 10.3 that doesn't need a
separate Postfix package.

If you have some patience, Marcus might have some packages
at the end of this 
week (22 Oct).  You could than install these packages and
help testing that 
those package are okay!

> My current server is completely functional but getting
a little out of
> date, so I'm looking to do something soon.


-- 
Richard Bos
Without a home the journey is endless

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Op zondag 14 oktober 2007 08:00, schreef Gunnar Wrobel:
> > How much work am I looking at?
>
> A lot. It took me about half a year to get the first
Kolab2/Gentoo
> version that was clean enough to install for somebody
other than me to
> install. It might be easier now but it is still far
from trivial. The
> patching is not really a problem. I believe
configuration and
> packaging are the main problems.

But in Eric's case we (Marcus and me) have already care of
this.  So, it is 
now mostly getting to know what you changed to the kolab
files/packages and 
adapt the opensuse spec files to it.

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Hi,

Op Sunday 14 October 2007 08:00:10 schreef Gunnar Wrobel:
> > Hooking in with Horde is also important to me.  I
am using Horde IMP and
> > the Contact/Calendar SyncML stuff right now.
>
> The Horde patches are also in the directory given
above. Are you using
> Horde with a Kolab server right now? I'd not expect
SyncML to work
> with the Kolab drivers at the moment. The changes added
to the Horde
> share system still pose some problems to the internal
API calls.

Would horde gain something when using http://www.opensync.org ?
As I see it, it would mean that the horde devs would only
need to care for the 
interface and anylonger for the interaction between devices
and the PC.

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Richard Bos <mlradoeka.nl> writes:

> Hi,
>
> Op Sunday 14 October 2007 08:00:10 schreef Gunnar
Wrobel:
>> > Hooking in with Horde is also important to me.
 I am using Horde IMP and
>> > the Contact/Calendar SyncML stuff right now.
>>
>> The Horde patches are also in the directory given
above. Are you using
>> Horde with a Kolab server right now? I'd not expect
SyncML to work
>> with the Kolab drivers at the moment. The changes
added to the Horde
>> share system still pose some problems to the
internal API calls.
>
> Would horde gain something when using http://www.opensync.org ?
> As I see it, it would mean that the horde devs would
only need to care for the 
> interface and anylonger for the interaction between
devices and the PC.

I think Horde itself would not gain much. They have SyncML
support
within Horde at the moment and it seems to work for some
models. From
the point of view of a PHP web application it makes sense to
provide
this within the framework provided by PHP rather than having
the admin
compiling a binary which you won't be able to do on a plain
web
server. 

My impression about opensync is, that it is also still in
very heavy
development. I tried to use their SyncML client for some
testing and
simply failed. They seem to know that though 

But the project seems to have a good direction and I can
easily
imagine that the Kolab project in general can profit from
that. If
we'd have a good python-kolab library it would be trivial to
write a
syncml python plugin to make Kolab a SyncML server:

http://opensync.org/browser/plugins/python-module
/src/sample.py

Cheers,

Gunnar

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Gunnar Wrobel wrote:
> Hi Eric,
>
> Eric K <eknuds-kolabknudstrup.org> writes:
>   
> Right, the postfix patches went in with postffix-2.4.0
so there is no
> patching needed.
>   
Great!
> The Horde patches are also in the directory given
above. Are you using
> Horde with a Kolab server right now? I'd not expect
SyncML to work
> with the Kolab drivers at the moment. The changes added
to the Horde
> share system still pose some problems to the internal
API calls.
>   
That's a bummer.  I wonder which would be more work. 
Getting another
front to work (such as Funambol) or updating the Horde
SyncML
implementation.
Right now I'm using Horde with the MySQL backend.
> I guess they are also interested in OpenSuSE 10.3. So
maybe there is a
> chance to collaborate.
>   
> Richard sent me a reply, so yeah, I'd like to assist in
the effort
> somehow.
I'm starting a new job in a couple of days so I may not have
an excess
of time and energy.
I think what I'd like to do at least is try to build a
verson of the
core Kolab package for 10.3 that doesn't need a separate
Postfix package.
My current server is completely functional but getting a
little out of
date, so I'm looking to do something soon.

Eric

-- 
It was the Law of the Sea, they said. Civilization ends at
the waterline. Beyond that, we all enter the food chain, and
not always right at the top.
Hunter S. Thompson 

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Eric Knudstrup <ericknudstrup.org> writes:

> Gunnar Wrobel wrote:
>> Hi Eric,
>>
>> Eric K <eknuds-kolabknudstrup.org> writes:
>>   
>> Right, the postfix patches went in with
postffix-2.4.0 so there is no
>> patching needed.
>>   
> Great!
>> The Horde patches are also in the directory given
above. Are you using
>> Horde with a Kolab server right now? I'd not expect
SyncML to work
>> with the Kolab drivers at the moment. The changes
added to the Horde
>> share system still pose some problems to the
internal API calls.
>>   
> That's a bummer.  I wonder which would be more work. 
Getting another
> front to work (such as Funambol) or updating the Horde
SyncML
> implementation.

Updating the Horde SyncML implementation. I already looked
into this.

> Right now I'm using Horde with the MySQL backend.
>> I guess they are also interested in OpenSuSE 10.3.
So maybe there is a
>> chance to collaborate.
>>   
>> Richard sent me a reply, so yeah, I'd like to
assist in the effort
>> somehow.
> I'm starting a new job in a couple of days so I may not
have an excess
> of time and energy.
> I think what I'd like to do at least is try to build a
verson of the
> core Kolab package for 10.3 that doesn't need a
separate Postfix package.
> My current server is completely functional but getting
a little out of
> date, so I'm looking to do something soon.
>
> Eric
>
> -- 
> It was the Law of the Sea, they said. Civilization ends
at the waterline. Beyond that, we all enter the food chain,
and not always right at the top.
> Hunter S. Thompson 
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users