News for hackers. Stuff that matters.
Re:Winding down my Debian involvement by wbl on Sunday March 10, 2019 @06:43PM (#19355172)
Try macports for a BSD style packaging for the mac.
Re:Winding down my Debian involvement by h1d on Sunday March 10, 2019 @09:40PM (#19356040)
What's the advantage of using macports over Homebrew?
Re:Winding down my Debian involvement by bhaak on Monday March 11, 2019 @05:00AM (#19357564)
For example proper runtime dependency management?

Try updating a single homebrew package to a new major version and watch the other homebrew packages depending on it breaking.

To be fair, that's not a problem unique to homebrew. Gentoo used to break runtime dependencies, too. Although that was a long time ago. Nowadays libs used by other programs are preserved and only deleted when all dependencies have been updated, so breakage no longer occurrs.

Re:Winding down my Debian involvement by mschuster91 on Tuesday March 12, 2019 @07:18AM (#19367037)
For one, it works just fine on multi-user Macs as it installs software under the uid/gid of the user who installed Homebrew somewhere under /usr/local whereas Homebrew installs it the proper way as root:admin and doesn't create a shitload of permission problems.
Re:Winding down my Debian involvement by AgentME on Tuesday March 12, 2019 @05:39PM (#19373328)
I can't understand whether you're saying Homebrew does it right or not on multiuser systems.

I have a lot of trouble with Homebrew on multiuser Mac systems. Running `brew install ...` or `brew update` as anyone but the user who originally installed Homebrew almost always fails because of permission errors (or it successfully installs, but then causes permission errors in the future for the user who installed Homebrew). Whenever I need to use Homebrew commands now, I use `sudo -iu otheruser` to switch to the user account who first installed Homebrew in order to avoid the permissions issues. I'm really baffled that Homebrew doesn't support the multiuser system case. Is it so rare to share a system nowadays? I've had this issue on multiple Macs and fresh installs, so I don't think this is some fluke bug.