[pkg-kolab] Re: [Pkg-Cyrus-imapd-Debian-devel] Kolab and cyrus
Henrique de Moraes Holschuh
hmh at debian.org
Fri Jan 13 03:20:05 UTC 2006
On Thu, 12 Jan 2006, Sven Mueller wrote:
> While it would certainly be possible, I would personally not want to get
> my hands dirty on that.
> The reason for this is simple:
> While I previously assumed (like Henrique) that the kolab patches would
> mostly add some vendor annotations and other simple (i.e. not too risky
> or complex) changes, the patches recently shown proved to be highly
> risky and asking for troubles (except for the ones I already applied).
> Disabling checks, allowing @ inside hierarchies, allowing previously
> unwanted characters in folder names really doesn't make much sense to
> me. And I don't see why kolab should require such changes (if it does,
> it seems like a serious design flaw in kolab).
If you feel unconfortable with the idea, then we won't do it. This must be
an unanimous decision on the Cyrus team, or it just wouldn't be right.
So, it is time for plan B, then. Kolab will need to maintain its own fork
of the cyrus packages (and I do mean a complete fork).
We can change the cyrus packages, IF there's a need to, so that it gets
easier for the kolab team to maintain the forked package.
In other words, that would mean we would help the kolab guys to make it
easier for them to have a separate package they create by importing our
latest source and adding their patches on top, patching debian/* stuff so
that it generates and works with kolab-* packages, and adding their
Sorry guys, I know this is somewhat less cooperation than the kolab team
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
More information about the pkg-kolab-devel