* Create the empty save folder on install.
* Deparallelize the build, since the master build runs a bunch of
nested makes, and we want the products to come out in-order.
MCrypt is a replacement for the old crypt() package and crypt(1) command, with
extensions. It allows developers to use a wide range of encryption functions,
without making drastic changes to their code. It allows users to encrypt
files or data streams without having to be cryptographers. Above all, it
allows you to have some really neat code on your machine. :)
Axel tries to accelerate downloads by using multiple connections (possibly to
multiple servers) for one download. Because of its size, it might be very
useful on bootdisks or other small systems as a wget replacement.
Thou shall not bump a packaging system's erlang version before it's released
even though you love to live on the edge.
Signed-off-by: Max Howell <max@methylblue.com>
Agreed, Homebrew sticks to stable releases in the main url, the @head url is used for cutting edge.
Well, I guessed keg_only would have issues.
Here, glib assumes GNU gettext will be in the same path as itself. Which would
be true if we symlinked gettext into the tree, but we don't to avoid conflicts
with the BSD version: /usr/lib/libgettext.dylib
We'll have to do this a lot, so I need to figure out how to automate it, or
how to avoid doing this kind of thing altogether.
Ruby is not natively threaded; there is absolutely no reason to build against
pthread unless you intend to link against libraries themselves built with
pthread (tcl/tk). More information: http://blogs.sun.com/prashant/entry/ruby_and_enable_pthreads
As far as I can deduce, the source of that flag is in Dan Benjamin’s article,
here: http://hivelogic.com/articles/ruby-rails-leopard
However, he provides no explanation for its use, and did not respond to
commentors’ requests for said explanation; on top of that, I can find no useful
references anywhere else. Hence, removing it.
Unfortunately, dealing with them requires quite a bit of shell configuration.
I offered the best documentation of this configuration that I could, but it’s
fairly verbose and a bit repulsive… unfortunately, the other option (attempting
to preform the setup automatically) turns out to be even messier, and prone to
mistakes to boot.
Shorten reduces the size of waveform files (such as audio) using Huffman
coding of prediction residuals and optional additional quantisation. In
lossless mode the amount of compression obtained depends on the nature
of the waveform. Those composing of low frequencies and low amplitudes
give the best compression, which may be 2:1 or better. Lossy compression
operates by specifying a minimum acceptable segmental signal to noise
ratio or a maximum bit rate. Lossy compression operates by zeroing the
lower order bits of the waveform, so retaining waveform shape.
Old formulas are valid, but should be maintained in a separate branch if
that's what is needed.
The exact way we are going to do this is not yet agreed on.
Eg gettext gets added into LDFLAGS, INCLUDE and that. I hope I got everything
that is typical. Prolly not. But we'll find out.
Made readline keg_only because the BSD version is provided by OS X, and I
don't want bug reports that are tricky to solve due to unexpected differences
between the two.
