There are lots of minor changes, but nothing major IMHO. The reason for bumping the minor version are a couple of breaking changes: - Disable SHA-1 checksum support in formulae - Disable running Homebrew as the root user (e.g. sudo brew) - Bottles with _or_later tags no longer use _or_later in their filenames so the existing bottle can be reused
Homebrew 1.1.0
11–20 of 216 posts
Re: Homebrew 1.1.0
#12Always good news to see progress in Brewland. I personally do not like having it installed in /usr/local and have ensured it never is on my installation, but I've not had the chance to ever discuss with one of their team why they do it and what things may possibly explode by not having Brew installed to /usr/local
For C libraries, having it in /usr/local is a benefit, since many already default to looking there, like cmake and autoconf scripts. Otherwise you have to fix that for many build scripts. While I share your misgivings about sticking stuff like this at the "system" level, I think they are right to do so in this case, for simplicities sake.
Re: Homebrew 1.1.0
#13There are lots of minor changes, but nothing major IMHO. The reason for bumping the minor version are a couple of breaking changes: - Disable SHA-1 checksum support in formulae - Disable running Homebrew as the root user (e.g. sudo brew) - Bottles with _or_later tags no longer use _or_later in their filenames so the existing bottle can be reused
Side-topic: Shouldn't the breaking changes be enough reason to bump the version to 2.0?
Re: Homebrew 1.1.0
#14There are lots of minor changes, but nothing major IMHO. The reason for bumping the minor version are a couple of breaking changes: - Disable SHA-1 checksum support in formulae - Disable running Homebrew as the root user (e.g. sudo brew) - Bottles with _or_later tags no longer use _or_later in their filenames so the existing bottle can be reused
Side-topic: Shouldn't the breaking changes be enough reason to bump the version to 2.0?
Re: Homebrew 1.1.0
#15Always good news to see progress in Brewland. I personally do not like having it installed in /usr/local and have ensured it never is on my installation, but I've not had the chance to ever discuss with one of their team why they do it and what things may possibly explode by not having Brew installed to /usr/local
At least you're missing out on bottles (pre-built formulae) when your prefix is not /usr/local. EDIT: The rationale for using /usr/local has been explained in the FAQ: https://github.com/Homebrew/brew/blob/master/docs/FAQ.md#why...
1. /usr/local/bin is already in your PATH
But not /usr/local/sbin, which I had to add anyway. 2. Tons of build scripts break
Not that much anymore, and gems can now be configured much more easily thanks to bundler. It's indeed a chore to tell configure to link against this or that, but most of the time you just build a package anyway (trivial with pacman/abs) for things to be managed. 3. no need to worry about messing up existing tools.
But many third party tools install stuff in /usr/local. Also, SIP prevents any mess from happening to system stuff.Also, regarding sudo:
But do you trust the multi-megabyte Makefile that Homebrew runs?
No I don't, that's why make/make install gets run as a regular user but under fakeroot when packaging with, say, pacman/abs.Running the install phase as root allows the package manager to make things just work, such as installing OpenVPN (which depends on tuntaposx kexts), or install daemons under their own user and have them launched on system boot (not user login) by /Library/LaunchDaemons, or install Python under /Library/Frameworks (which ironically, brew builds as a framework but stores somewhere else).
Again, those are tradeoffs and it's good that a stance is taken either way.
Disclaimer: long-time tentative maintainer of Arch OS X
Re: Homebrew 1.1.0
#16Earlier quoted context omitted.
For C libraries, having it in /usr/local is a benefit, since many already default to looking there, like cmake and autoconf scripts. Otherwise you have to fix that for many build scripts. While I share your misgivings about sticking stuff like this at the "system" level, I think they are right to do so in this case, for simplicities sake.
/usr/local is explicitly for user/administrator managed software versus /usr being for system managed stuff, it's the correct location for this on any UNIX/POSIX-like system.
For me these locations are an artifact of multiuser systems days, it's generally more desirable for me to store most stuff in my home directory, such that when I upgrade computers, there's only one thing to copy over.
Re: Homebrew 1.1.0
#17There are lots of minor changes, but nothing major IMHO. The reason for bumping the minor version are a couple of breaking changes: - Disable SHA-1 checksum support in formulae - Disable running Homebrew as the root user (e.g. sudo brew) - Bottles with _or_later tags no longer use _or_later in their filenames so the existing bottle can be reused
Side-topic: Shouldn't the breaking changes be enough reason to bump the version to 2.0?
Re: Homebrew 1.1.0
#18Homebrew maintainers are doing a fantastic job, made my life as a developer so much easier! I wanna use this opportunity to "publicly" thank them!
Re: Homebrew 1.1.0
#19Re: Homebrew 1.1.0
#20Earlier quoted context omitted.
Side-topic: Shouldn't the breaking changes be enough reason to bump the version to 2.0?
Not really. Signatures should be SHA256 already, you shouldn't be running as root (which as always been frowned upon).
Only in the Homebrew backwards-day world is having globally installed software not owned by root "frowned upon".