Hi! > 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.
Thank you for that. This can be an important application in the ports tree. > * 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? It's uncommon and there are no other ports doing this. To get it to build it's OK, but in the long run, this has to adapt. > * 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. >From what I know, this is approx. one magnitude (10x) larger than anything else. > (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? A make that does a git clone is probably a bad idea, the ports framework has no hooks for that, as far as I understand. Is there any kind of release process ? Some sort of code modularisation ? > Would this be a problem for the FreeBSD build cluster > infrastructure to create the packages?, ...) It would be a challenge, yes. > * 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've not found a port that does a git clone, so I think putting some git clone somewhere as a .tgz would be a easier start. > This is the right place to get help started in porting? FreeBSD has so > much mailing lists :-) Yes, it is. But I can tell you, this is a huge task! -- [email protected] +49 171 3101372 4 years to go ! _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
