Date: Mon, 18 Feb 2013 08:41:44 -0800 (PST) From: Paul Pathiakis <pathiaki2@yahoo.com> To: "ports@freebsd.org" <ports@freebsd.org> Subject: Fw: zimbra Message-ID: <1361205704.88885.YahooMailNeo@web141403.mail.bf1.yahoo.com> In-Reply-To: <256596676.84494.1360914987018.JavaMail.root@zmail.bubble.eu> References: <886358896.84440.1360914187935.JavaMail.root@zmail.bubble.eu> <256596676.84494.1360914987018.JavaMail.root@zmail.bubble.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A=0A----- Forwarded Message -----=0AFrom: Martin Sol=C4=8Diansky <solk= o@solko.sk>=0ATo: pathiaki2@yahoo.com =0ASent: Friday, February 15, 2013 2:= 56 AM=0ASubject: zimbra=0A =0A=0Ahey,=0AI am trying to get a complete port = built.=0A=0AI've seen the incredible effort that you put in and I believe i= t to be VERY CLOSE to a complete port build.=0A=0AI have been in contact wi= th the FreeBSD ports people and some have expressed an interest in getting = this to be a complete and sanctioned port.=0A=0APlease tell me that you're = interested in finishing this to completion.=0Aonce again, zimbra forums not= ification confuse me. i got private message notification on feb 15th, 6 day= s later :(.=0Ai can tell you that zimbra on freebsd is the same zimbra you = can run on linux nowadays. university mailserver has been happy for some ti= me now :). however, with a complete port build there are some major issues:= =0A1) '/opt/zimbra' is hardcoded. seriously, hardcoded in lots and lots of = parts of code. you can do a patch that will change this but it's very very = bad idea in the long run. the maintenance would kill you. putting stuff out= side /usr does not comply with freebsd standards. you can circumvent via mo= unt_null but i doubt that freebsd people will approve it.=0A2) some librari= es/versions, perl modules are simply NOT available in the ports collection = and if they are there you just cannot reuse them inside the base system sin= ce zimbra hardcodes stuff into them. there is a reason why zimbra team uses= specific versions of the third party software and i somehow learnt the har= d way :-). not to mention linking.=0A3) port upgrade would be a simple nigh= tmare. you have to use the provided zimbra-upgrade script (or spent ages to= do it your own way) and upgrade simply deletes all the binaries.. and repl= ace them.=0A=0Athat being said, i am well capable of creating an initial po= rt (hell, i started that long time ago and then just gave up) but i would n= eed constant help. i don't have time to maintain it. and maybe i even lack = some skill to do that. and i don't think that it can be done "properly".=0A= some time ago i offered zimbra team i would rework their build process so t= hat it becomes more.. transparent. well, i don't have the time now but prio= r to creating the port it would help a great deal if the zimbra team could = just incorporate slight changes (include placeholders for the patch in the = code, create ONE CONFIGURATION FILE FOR EVERYTHING (yes, caps)). that way y= ou could do only slight alterations. simply change "master dir" and you are= done (tbh, they use $ZIMBRA_HOME variable most of time.. and then.. they j= ust switch to /opt/zimbra :))=0A=0Aso there you got your very first step. f= or several years the patch just "added" support for freebsd compilation whi= le changing nothing for other platforms. i gave up in the last release and = just hardcoded it 'cos once again i lack time. contact freebsd ports people= , tell them to ask zimbra people to offer some help (they very friendly pre= -vmware - dont know now).=0Athe second step is finding someone who is inter= ested in maintaining the port. i can do the patching for new versions but i= simply won't handle the agenda (compatibility with other freebsd versions,= compilation, alteration bla bla otherworsending in -ion).=0A=0Ai will try = to prepare the newest zimbra version (8.0.2) patch and we can try the to ma= ke it happen :-). thing is.. i have no fucking idea why zimbra can't just d= o a proper supported commercial edition. it was proven that it runs on free= bsd and it's somehow a very silly commercial model to exclude shitload of f= reebsd servers from their portfolio.=0A=0Alet's cure the disease, not the s= ymptoms.=0A=0Ayou can reach me on skype via solko_the_demigod handle. best = of luck to you,=0A=0As.=0A=0APS (sorry about the html email but i just don'= t think that in these days anyone uses device without html support - and th= at comes from someone using fbsd for past 13 years) From owner-freebsd-ports@FreeBSD.ORG Mon Feb 18 18:07:15 2013 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 446101F0 for <freebsd-ports@freebsd.org>; Mon, 18 Feb 2013 18:07:15 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2a00:14b0:4200:32e0::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 0D34FD08 for <freebsd-ports@freebsd.org>; Mon, 18 Feb 2013 18:07:15 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id AEDE0168D42; Mon, 18 Feb 2013 18:07:13 +0000 (UTC) From: Stefan Bethke <stb@lassitu.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Please commit ports/176207 Date: Mon, 18 Feb 2013 19:07:13 +0100 Message-Id: <BA237342-CD5C-4A0B-9CCD-FF8696355287@lassitu.de> To: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Cc: anes@anes.su X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 18 Feb 2013 18:07:15 -0000 Hi, if any ports committer would be willing to commit the maintainer's patch = in ports/176207, I'd appreciate it! Thanks, Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1361205704.88885.YahooMailNeo>