FreeBSD support being added to GlusterFS

[Harshavardhana]

>
> I can make the /usr/local/var/log/glusterfs directory and it gets much further.   That said, is there some special configure flags we should be passing in our version of the port to properly stuff glusterfs into /var instead?  Your email tends to imply that we should be passing —localstatedir, which we can certainly do no problem, I’m just wondering if that’s your long-term plan.  Again, this is our port:  https://github.com/freenas/ports/tree/freenas/9-stable/sysutils/glusterfs
>
> The fundamental issue with /usr/local is, again, that /usr/local is read-only on FreeNAS.  If there are configuration files that glusterfs expects to be modifiable, they can’t live anywhere in /usr/local, nor of course can any temporary files or log files.  We have made special provisions for /etc and /var such that those can be modified, so we basically just need to compile gluster as a “system service” and put it in the system directories (e.g. prefix is /, not /usr/local).
>

Ah now i get it - "/usr/local" is not a requirement for "GlusterFS" it
is a baggage of using "autotools" when during ./configure if you do
not specify --prefix - so for a standard installation under RPM it is
usually the following flags are used

# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=/usr/lib64

Since FreeBSD doesn't need "/usr/lib64" you could just use for packages

# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var

-- 
Religious confuse piety with mere ritual, the virtuous confuse
regulation with outcomes