Date: Sat, 28 Jun 2014 00:04:49 -0700 From: Harshavardhana <harsha@harshavardhana.net> To: Jordan Hubbard <jordanhubbard@me.com> Cc: freebsd-fs@freebsd.org Subject: Re: FreeBSD support being added to GlusterFS Message-ID: <CAAeUqd2iAMeoRvm5LYz4-L_KpvKhTgabhdsSvmpB2B7GR7T1hQ@mail.gmail.com> In-Reply-To: <EF01BB42-EEBE-4F59-A066-5C18E3F1CAC6@me.com> References: <C647EDA1-EA93-4A66-B59D-3B5F959DC0E0@gluster.org> <6ADBB2BF-C7E8-4050-9278-2565A63D2EA8@gluster.org> <20140627070411.GI24440@ivaldir.etoilebsd.net> <AB0CB58A-A93E-4DDA-8060-A2B183BBB6FD@turbofuzz.com> <20140627223456.GD34108@ivaldir.etoilebsd.net> <EF01BB42-EEBE-4F59-A066-5C18E3F1CAC6@me.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Maybe someone at FreeNAS it willing to take maintainership of this port in the >> ports tree? >> >> Jordan does this new port fits FreeNAS requirements? > > Something seems to have eaten the attachment - did you simply update the diff at http://people.freebsd.org/~bapt/glusterfs.diff ? If so, I can re-grab that and test it in FreeNAS easily tomorrow. > I would personally think that such a specific change of paths and configuration should be done directly inside GlusterFS. Currently the problem is that this is in-fact is a hardcoded path and doesn't honor ${PREFIX} - i can get this fixed appropriately GlusterFS upstream. This in-fact an issue on "NetBSD and OSX" ports too which do not honor "/var/lib" There are two options - A conditional check for GlusterFS for FreeBSD to use "/var/db/glusterd" instead? - Make it configurable and honor "--localstatedir" and one can pass --localstatedir=/var while building a package. -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAeUqd2iAMeoRvm5LYz4-L_KpvKhTgabhdsSvmpB2B7GR7T1hQ>