It's upsetting that Apple doesn't care about developers. Why is there no Apple maintained package management system? This results in having to turn to solutions like Homebrew, which -- while a valiant effort -- is completely insufficient for distributing state across multiple machines.
Homebrew 1.1.0
91–100 of 216 posts
Re: Homebrew 1.1.0
#92I absolutely adore Homebrew and can't thank the package maintainers enough. I think of all the times I battled with compiling some package, or installing it via MacPorts only to struggle updating it.
Never with Homebrew. So much <3
Re: Homebrew 1.1.0
#93Earlier quoted context omitted.
Ah, that is very good to know! Thank you! I will take a fresh look at homebrew. :-)
To perhaps save you some effort: we still ask you to chown e.g. `/usr/local/bin` which may or may not make it unacceptable to you.
(Reaching back into foggy memory...) The last time I installed Homebrew, I think I had the problem that `/usr/local/bin` didn't exist, and I didn't have write permissions for `/usr/local/` so I couldn't create it (w/out sudo/chown) etc. This, using Sierra.
Does that seem likely? Usual? What's the ideal solution?
Re: Homebrew 1.1.0
#94I know they're different platforms, but how does this compare to apt? Which is better?
In addition to this if anyone could compare this apple to that orange and tell me which is best I would be grateful
Re: Homebrew 1.1.0
#95Homebrew is what keeps me working on a Mac, plus now that Docker for Mac is out....
Re: Homebrew 1.1.0
#96This spyware is awesome! Love how they track everything you do with the use of environment variables.
Care to explain, or are you just rambling?
Re: Homebrew 1.1.0
#97I have very mixed feelings about homebrew. When it works, it is awesome, but when it doesn't it can be a serious nightmare. In particular, homebrew refuses to run under sudo. Instead, to instal in /usr/local it wants me to recursively chown /usr/local to myself, which is a Really Bad Idea (tm). I have mostly stopped using it for this reason. I understand that running a program that runs third-party scripts under sudo…
> Instead, to instal in /usr/local it wants me to recursively chown /usr/local to myself, which is a Really Bad Idea (tm).
Why is this a really bad idea for a personal machine? The only problems I can think of are some subdirectories that are conventionally given some other user ownership to make running a related server under a specific user, and the problem of putting potentially arbitrary probably unreviewed executables in a system-wide path. But the former problem is one you wrestle with anyway if /usr/local is owned by root. And the latter problem... you're going to have some path where you're putting all this stuff, and it's either going to be a personally owned or system owned path. The system-owned choice means giving your package manager sudo and having to run things with sudo (which, without attention, means giving the executables system-wide access). What other problems does a personally owned path create? What's the alternative?
Re: Homebrew 1.1.0
#98Earlier quoted context omitted.
Ditto. I install almost everything via brew and brew cask, and store the list of packages in git. It makes setting up a new machine a breeze. Thanks for all your hard work!
This is a cool idea! How does one go about doing this though? Is there a flag to output a text file with the names of installed versioned packages?
I use `brew bundle` for this.
Re: Homebrew 1.1.0
#99I have very mixed feelings about homebrew. When it works, it is awesome, but when it doesn't it can be a serious nightmare. In particular, homebrew refuses to run under sudo. Instead, to instal in /usr/local it wants me to recursively chown /usr/local to myself, which is a Really Bad Idea (tm). I have mostly stopped using it for this reason. I understand that running a program that runs third-party scripts under sudo…
Isn't it desirable to run builds as not-root? If you're concerned about safety, you could maybe "freeze" your homebrew install by chowning /usr/local back to root in between brew invocations.
Very much the reason why MacPorts requires sudo, so it can drop to a less-privileged "macports" user for builds, without putting your own user account at risk.
Re: Homebrew 1.1.0
#100Just a quick poll. Is anybody still using MacPorts or anything else? If so, why?
I use macports. No particular reason, it just works for me and I don't see any reason to switch. It also feels more BSD-like, which is a plus for me, though I didn't dig deep enough.