I have had a little poke around.
It seems a bit uphill to port, since we dont want stuff in /opt on freebsd, and the /opt/zimbra part seems pretty infiltrated in the makefile.
We want the port to take care of all the 3rd party dependencies, all of which are allready ported to freebsd so that the port will only build core zimbra stuff.
We will have to patch the ZimbraBuild/Makefile, and quite possibly alot more.
Unfortunately, the first time I ever installed tomcat was today. But I will most likely start building a test port tomorrow. As far as I can make out, the build.xml's in ZimbraServer and ZimbraWebClient for ast will have to heavyly patched aswell, so that configuration files can be made more freebsd like.
Are there any zimbra plans to make these more generic in the future? Less centered around 3rd party components being installed with the actually zimbra installation...
Wouldn't i be enough to just depend on them allready being installed? Would that even be neccessary? Couldn't you add say, openldap, after the zimbra install. As far as I can see, there is no linking of any zimbra code to any 3rd party software. As someone stated, its all perl and java.
It might be that I dont understand enough yet, im certainly no java or ast expert!
On freebsd, we would depend on the jakarta-tomcat55 port, and thus zimbra would have to be configured to install its tomcat conf in the default freebsd webapps dir, which is somewhere under /usr/local and also it would have to _not_ install tomcat under its own install dir (/opt/zimbra which under freebsd would have to be /usr/local/zimbra or something like that), as one example of the kind of stuff that needs to be patched. Same for the other 3rd party stuff.
The scripts installed in /opt/zimbra/bin would have to be more freebsd like, they are currently written to handle the "everything under /opt/zimbra" scenario.
Any help and or hints from the zimbra guys would be greatly appreciated.  |