Probably stupid question but: how do you update your version?
brew update
I just tried `brew upgrade` but that is upgrading not itself, but every package installed with it instead. >:-&
Homebrew 1.1.0
21–30 of 216 posts
Re: Homebrew 1.1.0
#22Probably stupid question but: how do you update your version?
`brew update` i imagine
Re: Homebrew 1.1.0
#23There 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
> Disable running Homebrew as the root user (e.g. sudo brew)
why? Just curious, because I always use macports with sudo.
Re: Homebrew 1.1.0
#24There 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
> Disable running Homebrew as the root user (e.g. sudo brew) why? Just curious, because I always use macports with sudo.
I assume it's because 1) it's not really needed, and 2) it prevents shady packages from executing scripts as root.
Re: Homebrew 1.1.0
#25Probably stupid question but: how do you update your version?
Pretty sure just brew update.
Re: Homebrew 1.1.0
#26There 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
> Disable running Homebrew as the root user (e.g. sudo brew) why? Just curious, because I always use macports with sudo.
IIRC because it could cause problems with overwriting system libraries in earlier versions, so it has long been deprecated.
Re: Homebrew 1.1.0
#27Earlier quoted context omitted.
Not really. Signatures should be SHA256 already, you shouldn't be running as root (which as always been frowned upon).
> which as always been frowned upon Only in the Homebrew backwards-day world is having globally installed software not owned by root "frowned upon".
Hmmm. The UNIX education that's been hammered into me since childhood has said "If you can do it as not-root, don't do it as root".
Re: Homebrew 1.1.0
#28Always 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.
One of the issues I recall comes from not using Homebrew exclusively. For example, installing GPG from package puts files in the same location, and I've had conflicts in the past. It's not always possible to use Homebrew exclusively, so I move it elsewhere to mitigate this possible problem.
Re: Homebrew 1.1.0
#29Re: Homebrew 1.1.0
#30Always 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
Where do you have it installed instead?
$HOME/.homebrew