I'm about to aquire a Pi to replace my mail server, and wanted to go with Kolab here, most likely using Raspian as a base. They have their own repo, but concentrate on i386 and amd64. Checking for support of the ARMHF architecture in general, and the Pi in special, I only found a lot of people asking whether it were possible – but answers, if at all, were only as detailed as "yes", "somebody/I did it", or "X should know (but X doesn't talk much)".
With X often being Andreas Cordes, I've of course checked his site for Kolab on ARMHF architecture – and indeed he's got a detailed description on how to build the packages. I don't want to start building packages everytime there are updates (I simply lack the time). So I'd prefer to go with the alternative he provides "for the impatient", mentioning his repository. Unfortunately, that ends with "then install with aptitude the metapackage kolab and solve the dependencies manually because I didn't override the priority in the packages information" (emphasis mine) – with no details on what to expect at that end: might be trivial or complex, and I'm afraid of the latter ;).
As for configuration: My "raw plans" are currently to have all software on the Pi directly (SDCard), while placing all data (and, if possible, specific configurations) on external disk – for "fast-and-easy switching" in case of "emergency" (hardware/software failures).
Has anyone successfully installed Kolab on a Pi, and can provide easy-to-follow steps?
As said, I'm thinking about using Raspian as a base. But not even having the hardware obtained yet, I'm open for other "starters" as well. Would be great if the instructions would also match for a BananaPi (which they should with Raspian; little differences or "unsureness" pointed out is fine), in case the performance of a RasPi fails the requirements ;)
Edit: as I was asked whether ARMv6 or ARMv7: with the former being rather "oddballs", I prefer the latter (again speaking for compatibility with the BPi). My main goal is to get Kolab running on it smoothly, with as few "trip hazards" as possible plus ease of maintenance.