1. 24

  2. 4

    I’m still somewhat incredulous that Homebrew has yet to include an officially blessed way of removing unused dependencies. MacPorts provides the optional port_cutleaves utility, at least.

    1. 3

      Linux support? Hmm

      1. 3

        Homebrew is referred to as Linuxbrew when running on Linux or Windows 10 (under WSL). So far the beta is going ok, here’s the homepage for details: http://linuxbrew.sh

        1. 2

          Cool! Though I am a bit confused: why not use the distribution’s native package manager?

          Edit: I guess they do explain it: http://linuxbrew.sh/#features

      2. 3

        Any time I see Homebrew now I think of the author flunking Google’s interview. Poor guy.

        1. 3

          Same. Actually, the discussion that happened around this was what made me generally swear off CS-trivia style interviews/interviewing.

          Tweet: https://twitter.com/mxcl/status/608682016205344768

          Follow-up: https://www.quora.com/Whats-the-logic-behind-Google-rejecting-Max-Howell-the-author-of-Homebrew-for-not-being-able-to-invert-a-binary-tree/answer/Max-Howell

          1. 2

            Wait, what? Link?

          2. 1

            I want them to keep the HOMEBREW_BUILD_FROM_SOURCE environment variable. I think it’s tasteful, and I love having local source code available from which I can learn and with which I can tinker. Also, building from source can help mitigate security breaches like the one that occurred with Homebrew Bottle generation in August 2018: https://www.theregister.co.uk/2018/08/08/researcher_found_homebrew_github_token_hidden_in_plain_sight/

            1. 1

              I think I would prefer to use Nix on OS X, but brew is just so, so simple. I hate the way they handle transitive dependencies (ie, not at all), but it Just Works™ and that has a certain virtue all its own

              ETA: Today I discovered “brew bundle”, which sort of handles exactly the situation that I asked for. Very nice! I am pleasantly surprised, which rarely happens with software.

              1. 1

                brew bundle just installs what’s specified in Brewfile to system-wide paths, unlike Ruby’s Bundler and Nix. Almost the same as having shell script with brew install … commands, not very useful.

                1. 1

                  Yes, it’s not as correct a solution as is Nix; but it is much better than my understanding of the status quo ante.