[Kolab-devel] Kolab on RaspberryPi

[hede]

> http://whvneo.blogspot.com/p/preparation.html

I did it nearly the same way. With small changes, for example 
using the Sources-file as the source for packages:

wget http://obs.kolabsys.com:82/Kolab:/3.2/Debian_7.0/Sources -O - | \
grep "Package:" | sed -e "s/Package: //"

... I think that doesn't matter. 

And it seems you came across some problems I had. A patched cyrus-imapd is in the repository, which won't build this way. (I assume, because your binaries do not include it)

I compile it manually: 
apt-get source --only-source cyrus-imapd
apt-get build-dep --only-source cyrus-imapd
cd cyrus-imapd-2.5~dev2014011701/  # version changes
dpkg-buildpackage -j4 -us -uc # quad core here, remove "-j4" on RasPi
cd ..

This should be done before or after all other packages, because it depends on heimdal-dev, while other kolab packages need libkrb5-dev and both packages are mutually exclusive.

But that doesn't matter either, because stock cyrus-imapd from Debian is fine for running kolab. Those kolab-cyrus-patches needed in the past (with Kolab 2) are upstream by now. (e.g. annotations, folder types, etc.) 
And the new features of the patched cyrus 2.4 or new cyrus 2.5 are not mandatory.

> I imagine you almost wish you could cross-build 
> the packages on some serious hardware. ;-)

There are HowTos for Raspbian Cross Compiling on x86 out there.

(For me that doesn't matter, my Cortex Quad Core builds kolab in minutes, not hours.)

> But as you have shown, there's often little reason for packages not to be 
> available for an architecture as long as the software is portable and cleanly 
> packaged.

Yes, he did. Great work. But - and please, excuse my simplemindedness - 
why didn't I show so some days before then, when I proclaimed doing the same!?
Maybe because my humble mind doesn't matter? 

[Sorry, I couldn't resist in alluding my overmuch usage of "doesn't matter" ;-) ]

regards
hede