Zimbra Port

[Torsten Zuehlsdorff]

Hello Ray,

> I am trying to create a port of the zimbra collaboration suite. I am in
> contact with upstream and they are actively helping in making a port
> happen.

That is really create. I wanted to start a Zimbra port myself, but was 
stuck with GitLab (and a bunch of others...) :D

> I have a couple of questions though:
>
> * Zimbra expects itself to be installed to /opt/zimbra. It is not easy
> to change that, /opt/zimbra is hardcoded in a lot of places. Its a
> longterm goal of mine to help clean that up, but it is not possible
> right now. Are there any problems with a package which installs to /opt?

Normally we just change the pathes of such ports.

> * The Zimbra source is huge, a git clone is about 13 GigaBytes. I am not
> sure on how source that big is handled correctly in ports. (e.g. is it
> OK that every make does a git clone and you have to wait until you get
> the 13 GB of data? Would this be a problem for the FreeBSD build cluster
> infrastructure to create the packages?, ...)

A git clone contains the complete development *history*. If a try to 
fetch a packet from their homepage it is "just" around 850 MB which 
should not be a problem.

> * On the porters handbook it says to fetch a tarball from http/ftp, is
> it also possible to directly work with git and clone a repository?

I'm not aware of such a way. But since there is a Git-Repo: isn't there 
a management tool like GitLab, which could provides tarballs? At least 
it is possible to set one up, clone the repo and provide it this way.

> This is the right place to get help started in porting? FreeBSD has so
> much mailing lists :-)

Yes, this is the right place. Feel free to contact me, i would gladly 
help (but need to finish some more stuff before).

Greetings,
Torsten