Re: Zimbra Port

[Bradley T. Hughes]

> On 01 Jun 2016, at 16:08, Torsten Zuehlsdorff  
> wrote:
> 
>> * 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.

There's also the --depth option to git clone that can help limit the size of 
the resulting checkout.

   --depth 
   Create a shallow clone with a history truncated to the specified
   number of commits. Implies --single-branch unless
   --no-single-branch is given to fetch the histories near the tips of
   all branches.

--
Bradley T. Hughes
bradleythug...@fastmail.fm

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Torsten Zuehlsdorff]

On 02.06.2016 07:41, Bradley T. Hughes wrote:



On 01 Jun 2016, at 16:08, Torsten Zuehlsdorff  
wrote:


* 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.


There's also the --depth option to git clone that can help limit the size of 
the resulting checkout.

   --depth 
   Create a shallow clone with a history truncated to the specified
   number of commits. Implies --single-branch unless
   --no-single-branch is given to fetch the histories near the tips of
   all branches.


Yes, but i doubt this could be a solution. The ports ship a distinfo 
file, which contains size and checksum of the distfiles for the port. 
This is not possible with a pure git.


But since this is open source: in the worst case we can create the 
distfiles by ourself and host them. I don't see this as stopper.


Greetings,
Torsten
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[rs]

Hi Jim,


I never would have thought of taking upon such a huge project alone, but 
Zimbra is reaching out and they actively want Zimbra supported on 
FreeBSD (at least Zimbra-FOSS) and I can count on their help.


Also they are restructuring their components because they want zimbra to 
be included in other repositories also (Ubuntu, Debian, RPM based, 
etc.). So with the help of Zimbra it may not be an impossible task.



Best

Ray


On 06/01/16 16:19, Jim Ohlstein wrote:

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.

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  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-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Mathias Picker]

Am 1. Juni 2016 16:19:56 MESZ, schrieb Jim Ohlstein :
>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  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-unsubscr...@freebsd.org"
>___
>freebsd-ports@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
>"freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Torsten Zuehlsdorff]

On 01.06.2016 16:30, Miroslav Lachman wrote:

rs wrote on 06/01/2016 15:47:

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).


I wish you a good luck with porting this beast! There were a couple of
attempts to do this in the past but none succeeded. You can search the
Zimbra and FreeBSD websites (forums).


Hey - this was the same for GitLab. Sometimes i wish there is a funding 
for projects like this ;)


Greetings,
Torsten
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Miroslav Lachman]

rs wrote on 06/01/2016 15:47:

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).


I wish you a good luck with porting this beast! There were a couple of 
attempts to do this in the past but none succeeded. You can search the 
Zimbra and FreeBSD websites (forums).


Anyway - it would be nice to have in working on top of FreeBSD with 
upstream support!


Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Jim Ohlstein]

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. 

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  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-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 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

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Zimbra Port

[Kurt Jaeger]

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!

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Zimbra Port

[rs]

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-unsubscr...@freebsd.org"

Re: Zimbra Port

[Paul Pathiakis]

Chris,

I dug into it hard just a few days ago.

Here's their issues:

Like most people who are solely Linux (I'm not solely anything, 25+ years in 
sysadmin, architecture, internet engineering, etc.), they don't understand 
where /opt came from and what its true, original purpose was.  (Additional OS 
enhancement software - directory was created circa 1990).  Most of the linux 
world believes that all additional software goes into /opt.

Happily, we have nullfs but more happily, ZFS.

ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever, solves 
this issue.  (In other words, poor use of auto-configuration tools and make 
variables that allow you to define a DESTDIR instead of hardcoding it.)  
Performing a softlink or other things causes the install to totally blow up.

They guy who did the attempt at FreeBSD installation, did a decent job at 
figuring this out.  Everything, performing his procedure works as almost as 
directed.  

Things that are not to be liked about it:

He builds specific packages for the install and bundles them up with the 
install.
He creates three packages for the install, the builddeps, rundeps and source.
He then almost forces you to use these packages and his 'blessed ports 
packages that he created to get it to install correctly instead of just using 
ports.

After all this is installed with pkg_add (I couldn't find any indication of 
pkgng work) The supporting software is installed and ready to go.

Now, you get to the Zimbra source.  (All 3 software bundles are tar'd and 
gzip'd)  Once the ZCS is unpacked, you run install.sh in its root directory and 
away it goes.  

Once you get by some very strange errors (DNS not configured but it was, you 
have to force it to be your domain, and some other strangeness), you work out 
those few issues and find no errors in the install log(s).  Awesome

The last part of it is the thing starts up and integrates everything  (This 
is something truly impressive:  Apache, OpenSSL (certs get gen'd) , LDAP, 
MySqeel, Postfix, all the spam, virus, etc packages that go with a mail system, 
and on and on.  It then tells me everything is running and I have to 
connect to https://host:7071. it just hangs at that point  *shrug*  

I've tried debugging it and I've tried over 10 times of going over possible 
errors.  Nothing.  I tried contacting the author but there seems to be an 
access issue.

I'll try again soon, however, my company is being built right now  so I 
have VERY, VERY LIMITED time.  (Yes, it's PC-BSD and FreeBSD based)  I was 
hoping to have a full collaboration suite for MS exchange and Outlook drop-in 
replacement and this looked very promising.  *sigh*

P.





 From: Chris Rees cr...@freebsd.org
To: Paul Pathiakis pathia...@yahoo.com 
Cc: po...@freebsd.org po...@freebsd.org 
Sent: Friday, February 8, 2013 2:23 PM
Subject: Re: Zimbra Port
 
On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote:
 Hi,

 It looks like they are s close here.  Can't ports pick this up and put it 
 in the collection?

 http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD

 If you look at the Zimbra site for threads there are quite few with people 
 asking for Zimbra on FreeBSD.

At a glance it's a little less trivial than picking it up and putting
it in the collection :)

It probably wouldn't be too difficult, but someone would need to make
a tarball of the sources available, which may have licensing issues...
perhaps you could ask the author how he made the packages?

Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Zimbra Port

[Jason Helfman]

On Fri, Feb 8, 2013 at 12:59 PM, Paul Pathiakis pathia...@yahoo.com wrote:

 Chris,

 I dug into it hard just a few days ago.

 Here's their issues:

 Like most people who are solely Linux (I'm not solely anything, 25+
 years in sysadmin, architecture, internet engineering, etc.), they don't
 understand where /opt came from and what its true, original purpose was.
 (Additional OS enhancement software - directory was created circa 1990).
 Most of the linux world believes that all additional software goes into
 /opt.

 Happily, we have nullfs but more happily, ZFS.

 ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever,
 solves this issue.  (In other words, poor use of auto-configuration tools
 and make variables that allow you to define a DESTDIR instead of hardcoding
 it.)  Performing a softlink or other things causes the install to totally
 blow up.

 They guy who did the attempt at FreeBSD installation, did a decent job at
 figuring this out.  Everything, performing his procedure works as almost as
 directed.

 Things that are not to be liked about it:

 He builds specific packages for the install and bundles them up with the
 install.
 He creates three packages for the install, the builddeps, rundeps and
 source.
 He then almost forces you to use these packages and his 'blessed ports
 packages that he created to get it to install correctly instead of just
 using ports.

 After all this is installed with pkg_add (I couldn't find any indication
 of pkgng work) The supporting software is installed and ready to go.

 Now, you get to the Zimbra source.  (All 3 software bundles are tar'd and
 gzip'd)  Once the ZCS is unpacked, you run install.sh in its root directory
 and away it goes.

 Once you get by some very strange errors (DNS not configured but it was,
 you have to force it to be your domain, and some other strangeness), you
 work out those few issues and find no errors in the install log(s).
 Awesome

 The last part of it is the thing starts up and integrates everything
 (This is something truly impressive:  Apache, OpenSSL (certs get gen'd) ,
 LDAP, MySqeel, Postfix, all the spam, virus, etc packages that go with a
 mail system, and on and on.  It then tells me everything is running and
 I have to connect to https://host:7071. it just hangs at that
 point  *shrug*

 I've tried debugging it and I've tried over 10 times of going over
 possible errors.  Nothing.  I tried contacting the author but there seems
 to be an access issue.

 I'll try again soon, however, my company is being built right now  so
 I have VERY, VERY LIMITED time.  (Yes, it's PC-BSD and FreeBSD based)  I
 was hoping to have a full collaboration suite for MS exchange and Outlook
 drop-in replacement and this looked very promising.  *sigh*

 P.




 
  From: Chris Rees cr...@freebsd.org
 To: Paul Pathiakis pathia...@yahoo.com
 Cc: po...@freebsd.org po...@freebsd.org
 Sent: Friday, February 8, 2013 2:23 PM
 Subject: Re: Zimbra Port

 On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote:
  Hi,
 
  It looks like they are s close here.  Can't ports pick this up and
 put it in the collection?
 
  http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD
 
  If you look at the Zimbra site for threads there are quite few with
 people asking for Zimbra on FreeBSD.

 At a glance it's a little less trivial than picking it up and putting
 it in the collection :)

 It probably wouldn't be too difficult, but someone would need to make
 a tarball of the sources available, which may have licensing issues...
 perhaps you could ask the author how he made the packages?

 Chris


I may able to take a look at this. I was a Zimbra Administrator and have
run into a number of issues that I can solve, and maybe can work with you
on the port.

mail/zimbra or java/zimbra lol. :)

-jgh

--
Jason Helfman  | FreeBSD Committer
j...@freebsd.org | http://people.freebsd.org/~jgh  | The Power to Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Zimbra Port

[Paul Pathiakis]

Gentlemen:

I created an account on the Zimbra site and sent mail to the OSS Engineer, 
Solko, who has done most of the attempted post.  I hope to hear from him soon 
and get this kicked off.

At the present time, I'm in the middle of performing the buildout of my 
infrastructure and products for Atlantis Services, my company.  I hope to do 
FreeBSD/PC-BSD proud. :-)

I hope that Ports can pick up the mantle and run with this once I get all the 
parties to the table.

(Heck, I've done an OK job over the years although OpenNMS (Thanks to 
getting Sevan to talk to ports) is not a complete port, the install is 
incredibly simple now...  FrontAccounting is getting many of my client 
QuickBooks users :-)  Zimbra could be yet another great addition to ports.  As 
I get more feedback from my clients as to their needs, we'll round out even 
more useful ports for the small business user. )

(Sure my site isn't up, word of mouth is keeping me busy enough. :-) )  


You gotta love the look of bewilderment:

Not Microsoft?
Free Office Suite?  (OO, of course)
No viruses?
No SPAM?
Free software?
No license fees?

It just keeps getting better.

So, here's hoping we can get this to go quickly  


P.




 From: Jason Helfman j...@freebsd.org
To: Paul Pathiakis pathia...@yahoo.com 
Cc: Chris Rees cr...@freebsd.org; po...@freebsd.org po...@freebsd.org 
Sent: Friday, February 8, 2013 5:31 PM
Subject: Re: Zimbra Port
 

On Fri, Feb 8, 2013 at 12:59 PM, Paul Pathiakis pathia...@yahoo.com wrote:

Chris,

I dug into it hard just a few days ago.

Here's their issues:

Like most people who are solely Linux (I'm not solely anything, 25+ years in 
sysadmin, architecture, internet engineering, etc.), they don't understand 
where /opt came from and what its true, original purpose was.  (Additional OS 
enhancement software - directory was created circa 1990).  Most of the linux 
world believes that all additional software goes into /opt.

Happily, we have nullfs but more happily, ZFS.

ZFS creating /opt/zimbra or creating a zpool and zfs'ing it, whatever, solves 
this issue.  (In other words, poor use of auto-configuration tools and make 
variables that allow you to define a DESTDIR instead of hardcoding it.)  
Performing a softlink or other things causes the install to totally blow up.

They guy who did the attempt at FreeBSD installation, did a decent job at 
figuring this out.  Everything, performing his procedure works as almost as 
directed. 

Things that are not to be liked about it:

He builds specific packages for the install and bundles them up with the 
install.
He creates three packages for the install, the builddeps, rundeps and source.
He then almost forces you to use these packages and his 'blessed ports 
packages that he created to get it to install correctly instead of just using 
ports.

After all this is installed with pkg_add (I couldn't find any indication of 
pkgng work) The supporting software is installed and ready to go.

Now, you get to the Zimbra source.  (All 3 software bundles are tar'd and 
gzip'd)  Once the ZCS is unpacked, you run install.sh in its root directory 
and away it goes. 

Once you get by some very strange errors (DNS not configured but it was, you 
have to force it to be your domain, and some other strangeness), you work out 
those few issues and find no errors in the install log(s).  Awesome

The last part of it is the thing starts up and integrates everything  
(This is something truly impressive:  Apache, OpenSSL (certs get gen'd) , 
LDAP, MySqeel, Postfix, all the spam, virus, etc packages that go with a mail 
system, and on and on.  It then tells me everything is running and I have 
to connect to https://host:7071. it just hangs at that point  
*shrug* 

I've tried debugging it and I've tried over 10 times of going over possible 
errors.  Nothing.  I tried contacting the author but there seems to be an 
access issue.

I'll try again soon, however, my company is being built right now  so I 
have VERY, VERY LIMITED time.  (Yes, it's PC-BSD and FreeBSD based)  I was 
hoping to have a full collaboration suite for MS exchange and Outlook drop-in 
replacement and this looked very promising.  *sigh*

P.






 From: Chris Rees cr...@freebsd.org
To: Paul Pathiakis pathia...@yahoo.com
Cc: po...@freebsd.org po...@freebsd.org
Sent: Friday, February 8, 2013 2:23 PM
Subject: Re: Zimbra Port


On 29 January 2013 15:22, Paul Pathiakis pathia...@yahoo.com wrote:
 Hi,

 It looks like they are s close here.  Can't ports pick this up and put 
 it in the collection?

 http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD

 If you look at the Zimbra site for threads there are quite few with people 
 asking for Zimbra on FreeBSD.

At a glance it's a little less trivial than picking it up and putting
it in the collection :)

It probably wouldn't be too difficult, but someone would need to make
a tarball

Zimbra Port

[Paul Pathiakis]

Hi,

It looks like they are s close here.  Can't ports pick this up and put it 
in the collection?

http://wiki.zimbra.com/wiki/Zimbra_on_FreeBSD

If you look at the Zimbra site for threads there are quite few with people 
asking for Zimbra on FreeBSD.

PLEASE! :-)

P.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Zimbra Port for FreeBSD.

[Eric De La Cruz Lugo]

Heads up.

voting poll for FreeBSD port for Zimbra.

http://www.zimbra.com/forums/showthread.php?t=1247page=9

greetings from Merida, Yucatan, Mexico.

Eric De La Cruz Lugo.


 

TV dinner still cooling? 
Check out Tonight's Picks on Yahoo! TV.
http://tv.yahoo.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]