Quote:
|
It's not a question of "not doing Zimbra on Solaris". I've spent a lot of time porting it already, a few months ago. I got all of third party ported and had to put it aside at the point of looking at the application itself (undoubtedly a smaller challenge). I have no objections to running a stable release on an unsupported O/S. But I see no point in getting involved in application issues (beta) in addition to platform issues.
|
Good luck then. Vast majority of thirdparty is already written to run on solaris, so it's not really porting, more of a build process that needs defining - there is the odd exception to this eg. perdition. Contrary to what one would think from essentially a java app, Zimbra was paradoxically a much bigger challenge. I'll try and produce patches as well, perhaps you can apply them to 4.x tree.
I hear what you're saying about not adding app beta issues to the platform issues, but I took the approach that if my hackjob ever ends up contributing to an official port, it certainly wouldn't happen in 4.x series but might end up in 5.x. Often in opensource world betas are more stable than the last releases, and as Zimbra themselves use 5.x internally I took it that it was stable enough to make it worthwhile. As we can't track against svn I don't have time to do more than one port. Running Zimbra on a new platform takes iterations of trial and error before it would become stable enough for production use. I don't see this happening in the 4.x series.
Quote:
|
At the time I did that work, the build system and documentation was half cooked. I hope it's improved.
|
It hasn't.
Quote:
|
There is no way forward at the moment, even if I wanted to start over, without sensible access to Z source.
|
Well, does make it more difficult!