Date: Wed, 01 Jun 2016 17:03:19 +0200 From: Mathias Picker <Mathias.Picker@virtual-earth.de> To: Jim Ohlstein <jim@ohlste.in>,rs+freebsd-ports@trust64.com Cc: freebsd-ports@freebsd.org Subject: Re: Zimbra Port Message-ID: <32E845C9-3FB8-4325-9C63-8E213DEA707F@virtual-earth.de> In-Reply-To: <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in> References: <74bdbdd0-0883-c7bd-fa00-996fca53f502@trust64.com> <9F871A7D-1A54-495D-B9E4-5056F2EECB91@ohlste.in>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 1. Juni 2016 16:19:56 MESZ, schrieb Jim Ohlstein <jim@ohlste.in>: >Sorry for the top post. > >We use Zimbra on an Ubuntu LTS VM with storage via iSCSI. > >Given the magnitude, I honestly don't think ports or packages is really >the way to go. I believe that most people use a dedicated (to Zimbra) >server or VM. I second this. There allready is a version of zimbra on FreeBSD and it's intentionally not a real port https://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD I used to use this, but I'm now running a CentOS instance just for zimbra. And I don't think zimbra outside of /opt is ever going to happen, it's coded into too many places. You might want to rethink this… Cheers, Mathias > >If I were to approach this project, I'd do it outside of ports, maybe >on github, or possibly as a VM image. > >That's not to say it can't be done, rather that a project of this size >requires a layout that is not native to FreeBSD ports, and it's so >massive with so many moving parts, having to comply with the ports >infrastructure, and to maintain it, is probably far more effort than >it's worth. > >Jim Ohlstein >> On Jun 1, 2016, at 9:47 AM, rs <rs+freebsd-ports@trust64.com> wrote: >> >> Hello List, >> >> 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. >> >> It would be my first FreeBSD port (although I have a lot of linux >knowledge and know how to create packages for .deb). >> >> My first steps involve right now making everything compile (Zimbra >includes *a lot* of libraries themselves instead of relying on the OS >to provide them). >> >> 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? >> >> * 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?, ...) >> >> * 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? >> >> This is the right place to get help started in porting? FreeBSD has >so much mailing lists :-) >> >> Thank you, >> Best >> RAy >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to >"freebsd-ports-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-ports@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32E845C9-3FB8-4325-9C63-8E213DEA707F>