Hello Otmar,
I just installed a kolab server (for testing purposes) on
etch.
The "Compile from source" stopped somewhere
inbetween, so i tried the openpkg-rpms for sarge.
Installed flawlessly and works fine.
HTH
Arnim Sommer
-----Ursprüngliche Nachricht-----
Von: Otmar Lendl [mailto:ol bofh.priv.at]
Gesendet: Montag, 13. August 2007 15:23
An: kolab-userskolab.org
Betreff: Kolab on Debian etch
Hello,
I'm currently evaluating / installing Kolab at work on
Debian etch
based systems.
There seem to be various options, each with its own
drawback.
* Compile from source ( openpkg )
I usually try to keep within the official debian packages
to get the
benefit of clean upgrades and quasi-automatic security
updates.
If that's what I need to do, ok. I'd just prefer not to.
* Use the kolab packages from etch
They seem to be quite outdated. See
http://qa.debian.org/developer.php?login=pkg-kolab-devel
lists.alioth.debian.org
* Use the kolab packages from "unstable"
I tried that last week: I got the basic system up
(slapd/cyrus were
simple, the webinterface needed massaging (php4 vs. php5,
Apache 1.3
vs. 2).
kolab-resource-handlers conflicts indirectly with
kolab-webadmin, and
the URL for the interface is konsistent (/admin vs.
/kolab-webadmin).o
(kolab-resource-handlers: Depends: libapache2-mod-php4 but
it is not
going to be installed)
I this haven't managed to get the postfix filters up.
(right now I'm
running a straight postfix config without all the hooks.)
* Junk etch and run sarge.
I'm not sure how current the packages are for sarge, but
some website
lists sarge as the base for some of the developers.
So: What's the consensus on this question? Any advise for
me?
Thanks,
/ol
--
-=- Otmar Lendl -- olbofh.priv.at -=-
_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users
|
