Homebrew is awesome. Comes close to apt.
Homebrew 1.1.0
191–200 of 216 posts
Re: Homebrew 1.1.0
#192Earlier quoted context omitted.
Of specific interest: "This deprecation was announced and these methods removed/undocumented before 1.0.0 was tagged so arguably it was not part of the public API when 1.0.0 shipped." I'm ambivalent. If I rev 1.0 - 1.1, then I'm going to assume the API won't change, even if I'm using undocumented and warning-spitting methods. But I shouldn't be doing that, I shouldn't roll in a minor update without at least reading t…
> I'm going to assume the API won't change, even if > I'm using undocumented and warning-spitting methods. And here I disagree, quite strongly. If I'm using "undocumented and warning-spitting methods" then I know what I have done is a hack and those methods could disappear or change at any time and I should proceed at my own peril.
>And here I disagree, quite strongly. If I'm using "undocumented and warning-spitting methods" then I know what I have done is a hack and those methods could disappear or change at any time and I should proceed at my own peril.
We're in complete agreement, actually. I'm just saying that I generally don't expect things like that to change on a point release, not that it can't, won't, or shouldn't. You're definitely juggling chainsaws if you're in a situation like that.
Re: Homebrew 1.1.0
#193I have mixed feelings about Homebrew. Don't get me wrong, it's great, good job everyone involved. It makes my OSX laptop a viable development option for me. Without Homewbrew I wouldn't use it.
Alas that's also the problem. It makes OSX so familiar that this one OSX machine has now crept into my collection of Linux boxes and won't leave (thank you iOS development). I guess if your only complaint is that the software is too good...that's a pretty great thing :)
Sometimes I wonder how valuable Apple thinks Homebrew is for them. Any info on how much they contribute to the project?
Re: Homebrew 1.1.0
#194Earlier quoted context omitted.
Agreed. Homebrew has saved countless hours for developers, I can't believe how many hours I used to spend installing/updating different versions for testing. Now we just run (>brew switch package version) done.
Whoaaa didn't know that command. This could replace something like say nvm?
It maybe could be hacked into replacing it but I'd not recommend it. Better to use a dedicated tool that handles this stuff more cleanly e.g. nvm.
Re: Homebrew 1.1.0
#195Earlier quoted context omitted.
The officially supported thing is: https://github.com/Homebrew/homebrew-bundle See my Brewfile in my dotfiles for how I use it to install my stuff: https://github.com/MikeMcQuaid/dotfiles/blob/master/Brewfile If you want to go a step further there's also Strap which will bootstrap your macOS system with some sensible defaults and install Homebrew, your dotfiles and your Brewfile: https://github.com/mikemcquaid/strap…
This is utterly brilliant! Thank you. I've been looking like this for quite a while. I'm still looking through it all, but I don't suppose you have a solution for setting System Preferences, particularly Trackpad settings and remapping the Caps Lock key to Ctrl?
I don't use it but https://github.com/benbalter/plister should do that. There's an open issue to integrate it with Strap, too: https://github.com/benbalter/plister/issues/2
Re: Homebrew 1.1.0
#196Earlier quoted context omitted.
> recursively chown /usr/local to myself As of 1.0.0: you don't need to do this any more and we don't ask you to.
I'm on an older version (0.9.5); how do I fix the ownership of my /usr/local tree? EDIT: I know how to `chown`, I mean more, what can I give back to root, what needs to remain under homebrew's control? Does the new version ship with a tool/command that does this?
`brew update` and check you've not hit the update bug: https://github.com/homebrew/brew#update-bug
We'll tell you what permissions you need to keep/remove. Alternatively, uninstall and reinstall Homebrew and similarly we'll tell you on permissions.
Re: Homebrew 1.1.0
#197Just a quick poll. Is anybody still using MacPorts or anything else? If so, why?
I still use macports! As for why, there are a couple of reasons. First, Macports is often the fastest at updating their ports database after new versions of an upstream are released. Next, I also like that Macports doesn't really rely on anything OS-X specific except for Xcode. So I don't need to worry about crap like whether some Python package will work with Apple's Python distribution, or whether installing a new…
Macports doesn't really rely on anything OS-X specific except for Xcode
And that's a big problem right there, I don't use xcode and its also a 15GB install!, so a waste to my small 128GB ssd.
Not to mention you will get nagging updates of a huge app you don't use, which takes lots of time to download and install.
Why doesn't macports make their pkg manager work just with the xcode cli tools? and for those pkgs that need xcode, tell the user they need to install xcode first.
Re: Homebrew 1.1.0
#198Earlier quoted context omitted.
You need to use `sudo` as a one-off thing when you install Homebrew. Our installer does that for you otherwise we'll prompt you with `brew doctor`.
Why don't you have your binaries installed in a user-owned directory like ~/brew or whatever, and then put that at the front of the path? Asking people to `chown` a system path is plainly a contravention of the principle of least privilege.
`~/brew` varies from username to username and requires us to be able to relocate all binaries so they reference the correct path. We do this for as many as possible but it's not possible for all of them.
Re: Homebrew 1.1.0
#199Earlier quoted context omitted.
> Error: No available formula with the name "texlive" > ... > You can install it with Homebrew-Cask: > brew cask install mactex And then `brew cask install mactex` works nicely.
Maybe they updated the error message. Here is what it said that last time I tried Homebrew: $ brew info texlive Installing TeX from source is weird and gross, requires a lot of patches, and only builds 32-bit (and thus can't use Homebrew deps on Snow Leopard.) We recommend using a MacTeX distribution: https://www.tug.org/mactex/
We did update it, yep.
Re: Homebrew 1.1.0
#200It is so much easy to make your code public for everyone to use on Homebrew. Great job maintainers!