* Added the '--with-sample-config' option. This will generate the sample
Asterisk config files in /usr/local/etc/asterisk. It creates backups of any
existing files first.
* Removed the patch that used curl instead of wget to download the sound
files. This doesn't appear to be required any longer (at least, the sound
files download correctly without it, where they didn't previously).
* Removed the '--host=x86_64-darwin' configure switch. Supplying this switch
to configure results in the warning, 'configure: WARNING: If you wanted to
set the --build type, don't use --host. If a cross compiler is detected then
cross compile mode will be used.', and building without the switch appears
to result in the correct architecture being targeted.
* Removed the manual creation of /usr/local/etc/asterisk. This directory is
created automatically.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Updated the install instructions in the caveats so that the default case
is installing under the user's own account, and note that you should
do 'mysql -uroot' to test the connection.
Added instructions on how to do a manual setup to any folder under any
user account.
Files go into share/postgresql and docs into share/docs/postgresql
instead of directly into share and share/docs.
Also include docs (man & html) which weren't being included in install
step of build (see
http://archives.postgresql.org/pgsql-bugs/2010-10/msg00156.php).
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Some changes to the way HDF5 is configured:
* The SZIP dependency is actually used
* C++ bindings are compiled by default as it requires no additional
dependencies.
New formula options:
* Build Fortran bindings although this disables the production of shared
libraries.
* Build a threadsafe HDF5 library, although this disables C++ and Fortran
bindings and causes a performance hit.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
Remove the 'data' folder from the prefix, so the setup script
will not try to create databases there. Putting databases
in the prefix instead of directly in /usr/local means they
get deleted on a MySQL update, which is not what you want.
Also allow use with either Lua or LuaJIT
This patch lets you install luarocks against either the original Lua
interpreter, or against LuaJIT. Lua and LuaJIT are ABI-compatible, so
the rocks that you install should be compatible with both interpreters.
So we we can use the same path for installed rocks, regardless of which
interpreter we build luarocks against. This just affects which
interpreter is used to run luarocks itself.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
The LuaJIT interpreter doesn't depend on the stock Lua interpreter; it
can be built entirely on its own. We also install a non-versioned link
to the interpreter, at #{HOMEBREW_PREFIX}/bin/luajit.
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
