Slashdot Mirror


Homebrew 2.0 is Here With Official Support For Linux and Windows (brew.sh)

Homebrew, a popular package manager for macOS, has released version 2.0 with official support for Linux and Windows 10 (with Windows Subsystem Linux). Cross-platform setup scripts just got a whole lot easier. Other highlights: Homebrew does not run on OS X Mountain Lion (10.8) and below. For 10.4 - 10.6 support, see Tigerbrew. This has allowed us to remove large amounts of legacy code.
Homebrew does not migrate old, pre-1.0.0 installations from the Homebrew/legacy-homebrew (formerly Homebrew/homebrew repository. This has allowed us to delete legacy code that dealt with migrations from old versions.
Homebrew does not have any formulae with options in Homebrew/homebrew-core. Options will still be supported and encouraged by third-party taps. This change allows us to better focus on delivering binary packages rather than options. Formulae with options had to be built from source, could not be tested on our CI system and provided a disproportionate support burden on our volunteer maintainers.

2 of 76 comments (clear)

  1. I’ve stayed away by 93+Escort+Wagon · · Score: 4, Informative

    I’m not sure their security model is fully baked. They claim sudo is bad; but their solution seems to be making /user/local/bin writable to everybody (and if you try to avoid this permissions change using sudo, homebrew will block it). And while they claim /user/local/bin is only the “preferred” install location, if you attempt to use a different directory you quickly find many basic things will break - so there’s no good way around this.

    --
    #DeleteChrome
  2. Re:Homebrew driving you to drink? by PhunkySchtuff · · Score: 3, Informative

    This project got momentum by trashing on MacPorts, although MacPorts has always worked fine for me. Homebrew will never be on my system, simply because of their shabby treatment of a good port system written by very good people.

    Not only is this poor form to trash the competition - I don't know that the competition even deserve this trashing. I've been using MacPorts since it was DarwinPorts. I've never experienced it not working, or doing anything that I didn't expect it to. In the early days there may have been some software that simply wasn't ported over, but it's always behaved itself when I've been using it.