Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Some formulae have local info/dir files from before 9610ff2, and
attempting to link their info/dir over PREFIX/share/info/dir caused
linking to fail.

share/info files were always being linked if they existed, regardless of
whether the user had HOMEBREW_KEEP_INFO set. This primarily affects
users with software built before
9610ff2e9e06931693f49d4377ee26c0e664c547.

This also fixes a bug in Keg#link_dir, in which a file would always be
linked if no argument was passed.

The regexp that handles skipping info files was only skipping
info/*.info files, but several formula would create info/dir files as
well. Since these conflicted with each other, Homebrew would error out
during the linking step.

The print wrapper which has its own `puts` broke this line; though with
the changes to `link` it isn't necessary any longer, so just remove it.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

In this case the user will simply have to delete all but one keg in order to use the command that uses ARGV.kegs.

Refs Homebrew/homebrew#11050.

If the link already exists exactly (well almost exactly) as we are about to correct it, then it's okay. Otherwise we error out. This is a safe choice, and really, the correct choice too.

This will prevent the tickets like Homebrew/homebrew#11050 from occurring.

Refs http://stackoverflow.com/questions/9762943

The system ln no longer outputs anything. Though the user can force its output with a --verbose of course. So in cases where it's not the usual of: not writable or existing file, we can ask the user to run with --verbose. I don't particularly like hiding its output, but it just confused the error IMO since it is creating a relative symlink the output was weird every time I've seen it in tickets.

I made a print wrapper so that the brew-link output doesn't get mucked up if an exception is thrown.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Since 5bddaf2e ("Stop supportinb `brew install --force`), the --force
argument is still useful but only to overcome the blacklist
restrictions. Document this.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Everyone calls it "nodejs" so not having an alias to this is dumb.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>

Fixes Homebrew/homebrew#10829.

Fixes Homebrew/homebrew#10958.

Again, "Homebrew" is changed to "homebrew" before rendering to the user.

See previous commit's explanation.

We allow homebrew/dupes for instance, rather than Homebrew/dupes. Because nobody likes shifting in the terminal.

In the process of doing this I discovered some case-insensitive filesystem bugs we have avoided before because I had the foresight to mandate lowercase in formula names. GitHub considers Homebrew and homebrew to be different (even though you can't create both). So we had to allow case insensitivity in tap input. I have made it now so the resulting directory however is lowercased, neatly avoiding the issue. And so we also downcase tap arguments when applying them to tap directories or formula.

The symlinks in Formula must be updated.

brew-update needs to be able to unsymlink removed stuff from taps too.

For when the symlink for a tap already exists and points to the thing we are about to symlink. This can happen, mostly because my code has sucked, but since the filesystem can be edited by the user at whim, it's possible then too.

Fixes Homebrew/homebrew#11018.

We warn if you are not running the latest Leopard or Snow Leopard.
(We do not currently check Lion or Mountain Lion versions.)

Signed-off-by: Jack Nagel <jacknagel@gmail.com>

Closes Homebrew/homebrew#8870.

Fixes:

$ brew tap adamv/alt
...blah blah blah..
$ brew tap josegonzalez/php
...blah blah blah...
Warning: Could not tap josegonzalez/php/php over mxcl/master/php

Where it should be "over adamv/alt/php".

So you can do e.g.

    $ brew install adamv<TAB>
    Display all 106 possibilities? (y or n)
    $ brew install adamv/alt/openss<TAB>
    adamv/alt/openssh     adamv/alt/openssl098  adamv/alt/openssl100

Signed-off-by: Jack Nagel <jacknagel@gmail.com>