17 ms·
Homebrew 1.0.0
- hmans 10y agoGood.
- petrikapu 10y agoHas opt-out Google Analytics had any help for your project so far? https://news.ycombinator.com/item?id=11566720 https://news.ycombinator.com/item?id=11566720
- kersten 10y agobrew update brew --version
- firegrind 10y agoThanks for adding the detail I hoped to get from the article
- icantdrive55 10y agoKersten is a nice name.
- kersten 10y agoThanks. icantdrive55 is equally romantic ;)
- gregpardo 10y agoReally what I wanted to. :/
- tibbon 10y agoMine gave me a permissions error, trying `brew doctor` now. I wonder if I have something configured incorrectly from a few years ago. I do with the update announcement page said how to best update (in case there were any major changes).
- ksherlock 10y agobrew update --force (if update errors prevented the migration)
- claar 10y agoThanks for this. Didn't work for me due to the "update bug" at https://news.ycombinator.com/item?id=12547579 https://news.ycombinator.com/item?id=12547579 , but the fix there worked.
- mkolodny 10y agoIn case anyone else command-finded for "update homebrew", this is how you update homebrew to the latest version (1.0.0).
- matt4077 10y agoAmong all the software I use, Homebrew must be the one giving me the least trouble. I have 100 installed packages and I don't remember the last time anything didn't work. Plus, for anything I care about, updates seem to always take less than a day, usually it's almost instantaneous. In comparison with MacPorts before, it's like night and day. npm/pip/mix/bundler all seem to periodically conspire to waste a few hours of my time (even though I can do that quite well on my own). NPM being the worst of the bunch. By a lot. About this much: `tree node_modules`
- philplckthun 10y agoSo npm is bad in your opinion, because it correctly handles different dependencies on packages with varying versions, screwing up? Or is the problem the vast js ecosystem? I don't think that "tree X" can be a good argument against using any kind of package manager.
- kminehart 10y agoIt's just popular to hate JavaScript and npm right now. It's not perfect, but it's not bad either.
- philplckthun 10y agoThis whole "JS and it's ecosystem is the worst"-meme is just awful. Same goes for the PHP counterpart. I think it's fine to search for better solutions for our backends, but there is no denying that 1) our browsers rely on JS and will do so for the close future, and 2) that there is an ecosystem for every programming language that can use it efficiently and proficiently.
- azdavis 10y agoYeah, I'm not seeing how "tree node_modules" is an argument against npm per se. Maybe one could argue npm, inc promotes the small-modules approach, but I don't think that's relevant to whether npm itself is a good package manager. No matter whether you think small modules are good or bad, I personally have experienced npm to at least manage them well. Admittedly, however, I've never actually worked on projects of any great size.
- _kyran 10y agoThanks to Mike and everyone else that has contributed to Homebrew. I couldn't imagine how difficult it would be managing command line programs on a Mac without it.
- tangue 10y agoI'm wondering if Macs would be as successful with developers without homebrew.
- rafadc 10y agoNo
- OskarS 10y agoIf it wasn't for Homebrew, I would not develop on a Mac.
- panglott 10y agoMac OS X came out in 2001, and there was a lot of immediate adoption by people using emacs and bash: It became the largest consumer distro of a Unix-based system overnight. (look for all the old articles about how to upgrade from tcsh to bash). Homebrew was successful because there were developers who wanted it. Is the Mac more successful as a developer platform because of it? Possibly.
- tangue 10y agoIt's fun to read all of this. I re-read John Siracusa reviews and some old blogs and yes, until Snow Leopard OSX was THE cool hackers' OS. And when Apple didn't invest in power users anymore, individuals took over.
- emdowling 10y agoThere has been a lot of talk in HN comments recently about Homebrew installing to `/usr/local`. With macOS Sierra, the user can no longer write to this folder without specifically owning it. Is there a security risk here and if so, whats the best workaround?
- elmigranto 10y agoNewer versions install in `/usr/local/Homebrew`, older versions "migrate" there: http://apple.stackexchange.com/questions/253404/how-does-homebrew-no-longer-need-ownership-of-usr-local http://apple.stackexchange.com/questions/253404/how-does-hom...
- emdowling 10y agoAwesome, thanks for that. Would be good for it to be listed on the article. It only tells you that it no longer requires ownership after you have been asked to give it for the migration.
- netheril96 10y agoI have a hard time understanding the "migration", even after reading all the related issues. Homebrew still writes into /usr/local/bin and /usr/local/Cellar, nothing different from the past. What exactly changes?
- oefrha 10y agoWriting to /usr/local/bin is not the same as writing to /usr/local. We don't drop a README.md in /usr/local anymore, for instance, and you can change the ownership of /usr/local back to root:wheel after the migration.
- jwarren 10y agoI've always installed to ~/.homebrew, and never encountered any problems.
- 10y ago
- Empact 10y agoThrowback to that one time Google wouldn't hire @mxcl. ;) https://twitter.com/mxcl/status/608682016205344768 https://twitter.com/mxcl/status/608682016205344768 Well done Mike and contributors! It's a great piece of work.
- sergiotapia 10y agoHe couldn't even ${college_level_gotcha}! No wonder he wasn't hired!
- Kequc 10y agoAfter it has been determined that there is a certain level of capacity to perform, then it should be about how excited they are to learn and integrate into the company's technology stack and culture. Technology stacks have become complex enough in recent years that it is a little bit unreasonable to expect a candidate to be familiar with all of it. The same way it is a little bit unreasonable that the developer would know or remember every college level gotcha you could throw their way. For instance what if they code in such a way that they haven't run into that problem in years as it is internalised. Or maybe they make use of tools that eliminate a lot of problems, such as TypeScript or similar. A good developer comes in many forms and increasingly often from all over the world.
- ssalazar 10y agoAccording to him. The only context is one tweet from one side of the story.
- itchynosedev 10y agoIt's hard for me to understand the issue with this. Google didn't hire the guy who wrote software that had a big impact on the community. Does it mean Google misses good engineers because of their less-than-ideal interview process, or simply Google hires only people who are a good fit for their organisation? Writing the overly bitter tweet surely won't help with improving hiring points. Seems highly unprofessional and childish.
- 10y ago
- VeejayRampay 10y agoHomebrew is a huge help that perfectly fills the niche it's intended for. Thanks for all people involved, you're time savers, which is pretty much the most sought after quality of a software project.
- pikachu_is_cool 10y agoExcept for loading the Ruby VM. Takes way too long.
- mikemcquaid 10y agoWhich is why for certain things like `brew --prefix` we now do it purely in Bash rather than using Ruby ;)
- barpet 10y agoWhy would bash be faster ? Would not you essentially call the same C lib stuff anyway ?
- s_kilk 10y agoIt would at least save the process-start overhead, plus loading the ruby vm and modules/gems.
- mikemcquaid 10y agoExactly. For a simple string comparison Bash is far faster (although Homebrew doesn't use require any gems, just FYI).
- s_kilk 10y agoGood to know, so did the speedup come mostly from not spinning-up the Ruby VM?
- princetman 10y ago"brew update Error: /usr/local is not writable. You should change the ownership and permissions of /usr/local back to your user account: sudo chown -R $(whoami) /usr/local . . . ==> Migrating HOMEBREW_REPOSITORY (please wait)... ==> Migrated HOMEBREW_REPOSITORY to /usr/local/Homebrew! Homebrew no longer needs to have ownership of /usr/local. If you wish you can return /usr/local to its default ownership with: sudo chown root:wheel /usr/local" You got to love the user experience of this! Thanks Homebrew team. <3
- oefrha 10y agoI see no problem in this. We need writing permissions to /usr/local to finish our migration (as we always did). Once you finish the migration we (hopefully) never write directly to /usr/local again.
- pivo 10y agoI think princetman was being sincere that he loved the experience. homebrew went to the trouble of telling us that we could restore the default permissions to /usr/local, that's nice.
- epenn 10y agoI'm fairly certain you misinterpreted that. He was complimenting the smooth process.
- princetman 10y agoIt was a compliment, as mentioned in other comments. I love the fact that it just doesn't error out, it offers a fix right there. It also humbly offers to surrender the rights to directories it no longer need. Coming from recent Dropbox helper agent debacle, I truly appreciate the philosophy behind this and applaud the team.
- moridin007 10y agoso smooth. much wow
- oefrha 10y ago
- sergiotapia 10y agoThank you guys for making my life as a software dev and end user infinitely easier. - brew install postgresql - brew install mpv The list goes on and on and on. You rock!
- danielsamuels 10y agoPostgres.app[1] would make your life even easier. :) [1]: http://postgresapp.com/ http://postgresapp.com/
- sergiotapia 10y agoI switched to use the homebrew version because I couldn't get the pg tools and such to work from the command line. Nobody got time for that. :P
- danielsamuels 10y agoFair enough, I've personally never had that experience.
- tibbon 10y agoAfter doing both homebrew and Postgresapp for a while, I've switched to using Docker to run it. It's really nice because then on a per-app basis I can have separate versions easily and all checked into version control.
- prh8 10y agoPostgres.app is "easier" to install but more trouble to develop with than properly installed Postgres. And "easier" means downloading an app, since it's quicker and fewer steps to install via Homebrew.
- tedmiston 10y agoIt's a convenient app but I'm very conscious of menu bar real estate, and mostly don't use it for the reason of adding an icon where the only interaction is launching / quitting it. I wish we had a better GUI for managing a user's daemons on OS X.
- Flimm 10y agoI'm excited about Homebrew potentially coming to Linux. When I first started using OS X more regularly, I was surprised by how better an experience OS X + Homebrew is compared to Ubuntu/Debian repositories + PPAs/third-party repositories.
- pcr0 10y agoIsn't it there already? https://github.com/Linuxbrew/brew https://github.com/Linuxbrew/brew
- Flimm 10y agoI don't know much about Linuxbrew, but that looks like a fork, not Homebrew officially supporting Linux.
- deleted 10y ago[deleted]
- mikemcquaid 10y agoWe're attempting to merge the two projects so eventually Linuxbrew/brew can go away. It's a relatively slow process, though.
- DeadBabyOrgasm 10y agoWhat about chromebrew [0] (homebrew for chrome os)? [0]: https://github.com/skycocker/chromebrew https://github.com/skycocker/chromebrew
- mikemcquaid 10y agoIt doesn't appear related so would be hard to merge.
- DeadBabyOrgasm 10y ago
- laurent123456 10y agoHomebrew is quite an achievement, it grew in complexity over the years, yet remained reliable and kept a user-friendly interface. It's also very simple to create packages, it took me less 30 min to learn how to create a package and to deploy it. In comparison last time I checked, creating deb packages is absurdly complex, and I usually just give up and provide a Bash file instead.
- _RPM 10y agoI find your statement laughable. Brew and Debian's package manager aren't even comparable.
- mikemcquaid 10y agoIt's easier to create packages for Homebrew but, as I'd be the first to admit, `apt-get` has far more advanced dependency management and resolution. They both have their strengths and weaknesses.
- laurent123456 10y agoapt-get has a wider scope but, in some cases, what it is needed for is to deploy a simple application, and there's no simple way to do that with Debian packages.
- deleted 10y ago[deleted]
- rogual 10y agoAs a user, Homebrew is a great experience. As a package maintainer, though, one thing surprised me: you can't make your package depend on a specific version -- even a major version -- of a library. So if MyApp uses YourLib 1.0, everything is fine until YourLib 2.0 comes out, at which point users doing `brew install myapp` will start getting cryptic compiler errors. I have no choice but to drop whatever I'm doing and make MyApp compatible with YourLib 2.0, which may even be impossible. It's just odd because otherwise Homebrew is so well designed. It seems like a weird omission. Edit: Some packages get around this by packaging major versions separately (qt, qt5) but most don't.
- rwl4 10y agoIt's for this very reason that I'm still one of those old-school guys who still uses MacPorts. I was horrified to see this, and in my brief time using it, it actually caused me real problems, so I went back.
- davb 10y agoI switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720 https://news.ycombinator.com/item?id=11566720 [2] https://github.com/Homebrew/brew/issues/142 https://github.com/Homebrew/brew/issues/142
- RodgerTheGreat 10y agoWow. Thanks for bringing this to my attention. I recently got a new mac and I decided to give brew a spin as my package manager. I was unimpressed with many aspects of the experience- for example, getting weird snarky messages and incorrect advice when I attempted to install texlive- but this seals it. Back to Macports it is. I'll be sure to tell others about this.
- emmelaich 10y agoI can see a point in the future where everything is installed via a homebrew-like process. Forget CPAN, CRAN, ports, pypi, go-get, rpm, apt, cabal, crate, opam, ... Just get it from github or similar with homebrew.
- s_kilk 10y agoDoubtful, homebrew doesn't do any kind of dependency management, so it would be a strict downgrade from pip, gem, cabal, etc Edit: See comment from rogual elsewhere in this thread - https://news.ycombinator.com/item?id=12547076 https://news.ycombinator.com/item?id=12547076
- mikemcquaid 10y agoThat's an exaggeration. We definitely do dependency management, we just don't allow formulae in core to pin against arbitrary versions of software because it often means security updates are never tracked. We are going to loosen this slightly but not dramatically: https://github.com/Homebrew/brew/issues/620 https://github.com/Homebrew/brew/issues/620
- s_kilk 10y agoThanks for the clarification. However, if Foo depends on Bar, will homebrew track the dependency so that I can't upgrade Bar to a version incompatible with the existing installation of Foo? I recall running into that issue a while back, and it gave the impression of version tracking being an install-time-only deal.
- mikemcquaid 10y agoIn homebrew/core and within taps we ensure those cases are handled by `revision`s and CI checks. Across taps this is harder and we're working on it.
- Keats 10y agoNix kinda does that, we use it for Go, it replaces pip and for system stuff.
- dudul 10y agoHomebrew is really great, and I recently discovered cask (I know, lame, but I'm a MacOS noob :) ) and it's so nice. No more downloading freaking dmg, mounting, dragging, clicking a bunch of popups, no more visiting the app store. How is this thing not integrated in MacOS yet?
- adrianN 10y ago> no more visiting the app store You answered your own question.
- faitswulff 10y agoAs a developer, I'm intimidated - Homebrew sets an extremely high standard for software 1.0 release quality.
- tedmiston 10y agoRemember how long Gmail was "beta"?
- tracker1 10y agoThe funny thing is how quirky the gmail settings look compared to the rest of gmail these days... it works, but it just doesn't quite fit. Though on the flip side, I don't like how much they changed contacts, and that I can't initiate SMS messages from contacts web ui anymore.
- Pastina 10y agoI had uninstalled homebrew this week because it stopped functioning. Out of nowhere, I started getting a ruby error related to a particular package and every CLI call would fail because of it. As someone who works with Go, it's sad to see an error bubbling up and not being gracefully handled.
- _d8fd 10y agoI had errors with Homebrew and Go this week. In both cases, it was an issue with Websense (also known as Forcepoint). Might your issue be related to that?
- isarat 10y agoShould I go for a clean install, considering the structural changes?
- isarat 10y agoShould I go for a fresh install, considering structural changes?
- adidalal 10y agoJust wanted to highlight that as of this release, all the core code for Homebrew-Cask (the sister project for GUI apps) has been (re)integrated into the Brew codebase. This should allow for tighter integration between the two and a renewed focus on making installing GUI apps as painless as possible! From a user/developer perspective, we've created a command line utility (`cask-repair`) to make version bumps as painless as possible. Would love to see more people using it [0], and we welcome suggestions and PRs (we have a few long-standing issues that have gone unaddressed, and fresh eyes are always good!) [0] https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md https://github.com/caskroom/homebrew-cask/blob/master/CONTRI...
- dcosson 10y agoLooking forward to checking this out. One issue I have run into with homebrew is that due to varying packaging choices as a project grows, I've seen stuff move back and forth from brew core to cask to neither, and the old ones stick around at the outdated version so you have to be careful when you tell people to install the thing (seen this happen with terraform for example, which a month ago when I last checked existed as a year-old version in a cask, a few months old version in core, and the current version wasn't available in either). It might be cool to also allow some kind of process for marking packages as deprecated and showing a warning or confirmation prompt if you try to install it, for the cases when maintainers start packaging in some different way that can't be supported by homebrew.
- adidalal 10y agoWe do have a `deprecated` caveat, but we rely on users to bring up that fact, as there's no way the maintainers can keep track of the status of every Cask. There's also a fairly large push and discussion about removing duplication between Homebrew core and Homebrew Cask, so you should see things improve. There should also be Formula -> renamed Cask migration at some point, the issue has been raised in brew-evolution. (We have basic Cask <-> Formula support already). Re: terraform specifically, looks like it's now in core, and `brew cask terraform` will know to do `brew install terraform` automatically.
- mirekrusin 10y agoBe aware of "update bug" If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run: ``` cd "$(brew --repo)" && git fetch && git reset --hard origin/master && brew update ``` I had to.
- OskarS 10y agoYep, me as well. Thanks!
- wonks 10y agoI also had to do this. Keep in mind that ```brew update``` might take a while to output anything when you do this (it did for me), and then it will ask you to wait while it migrates to a new directory.
- oefrha 10y agoJust want to point out that you could always add the --verbose flag to brew commands to see more progress information (in this case how brew calls git to update brew itself and each tap you have tapped, including the core tap).
- Bhullnatik 10y agoIt took me way too long of daily `brew update`s to notice something was wrong.
- tracker1 10y agoit's funny, but other than a few basic tools, most of what I get from homebrew is versionables (nvm, pyenv, etc) of other programming utilities, in that, I don't run brew update very often, usually only before installing something new via homebrew.
- STRML 10y agoYep, had to too. They released a revision with a broken update fn? Or did they force-push?
- FabHK 10y agoBrew is awesome. Note though that it gathers anonymous aggregate user behaviour analytics and reports to Google Analytics, see https://git.io/brew-analytics https://git.io/brew-analytics . You can opt out with brew analytics off
- OskarS 10y agoThat's a thing they shouldn't enable by default, but I don't mind it. As a developer, anonymous usage data has helped me out enough times. People! Be nice to your fellow developers! When something asks you to send anonymized usage data, do it!
- amorphid 10y agoI disagree. As a friend of mine said, "if you don't trust a software package, don't use it." I have paid exactly $0 for Homebrew. Reporting usage statistics makes it better, and I'm happy to be chip in to help out.
- mikemcquaid 10y agoThat's obviously fine for you to do but it's worth noting that we remove software that no-one uses where "no-one" is defined by "no-one using analytics". That's actually our main use-case for analytics.
- bm5k 10y agoStill not a good enough reason for analytics to be opt-out.
- falcolas 10y ago> we remove software Why? Personally, the only reason I would remove software from a repository is if it didn't work, impacted performance, or cost me an unreasonable amount of money/time. There's a really long tail for software packages.
- mikemcquaid 10y ago
- jason_slack 10y agoThank you Homebrew! As corny as this may sound. I rely on Homebrew to get my unix experience on OS X and not have to compile everything myself. Saves me time and is one less wrench in my development process.
- Keyframe 10y agoI have a stupid question. Is there a dogmatic way of listing installed things and sharing that with other brew? For example, I now list with brew list into a file and edit the file so that whole list is a big brew install. That way if I reinstall OS or go to another I can have same things.
- avitzurel 10y agoDon't know if there is but that's a great idea. I always had a pain of brew installing on new systems. Especially when you want to lock versions of some things (MySQL etc).
- StyloBill 10y agoNot sure if that's what you wanna do but you could do : "ls /usr/local/Cellar/ | cat >> myInstall.txt"
- sigjuice 10y agoWhy not "ls /usr/local/Cellar >> myInstall.txt" ?
- StyloBill 10y agoI use cat out of habit but yep, you're absolutely correct.
- Keyframe 10y agoI just do this for now: cat <(echo brew install) <(brew list) | sed ':a;N;$!ba;s/\n/ /g' > brew_install.txt It lists directly from brew, prepends brew install and then replaces all newlines with a space and outputs to brew_install.txt
- jfb 10y agoI use brew leaves instead of brew list for this sort of thing; as I usually don't care about the constituent transitive dependencies, only the final results.
- tbrock 10y agoI've worked with mike to maintain formula for years and he is always pleasant and on top of things in what is a very hectic job. Homebrew is such a good package manager (and not for the reasons any package manager is classically considered good). It's great because the community is so vibrant, the user experience is so well thought out, and the formula dsl makes so much logical sense. It's actually both a GitHub and Ruby showcase. Thanks homebrew team! Here to many more years of accessible packages on the Mac.
- mikemcquaid 10y agoThanks for the kind words, Tyler. You've been doing great work for us for a long time so the feelings are mutual.
- joshmanders 10y agoThank you Mike and team, seriously. Homebrew is a must have and I can't function on a machine that doesn't have it.
- stephenr 10y ago> not for the reasons any package manager is classically considered good You can say that again. Homebrew's dependency management is a fucking joke, to the point that it might as well not exist.
- tbrock 10y agoHonestly, it never seems to be a problem for me and I use homebrew extensively.
- freehunter 10y agoThat's the reason I stopped using Homebrew and plenty of other comments have said the same thing. Maybe it's changed recently, but last time I used it (about a year ago), dependencies were not cleanly resolved in every case.
- 10y ago
- sigjuice 10y agoFrom the announcement: Use new Ruby Macho library for reading and writing library macOS Mach O file locations. Why does Homebrew need to parse Mach-O files? Is this for fixing up shared library paths inside executables?
- woodruffw 10y agoAuthor of ruby-macho (the library being used) here: Yes, exactly. During bottle installations, we need to be able to relocate dylib references and install names so that they're relative to the Homebrew prefix.
- DerDangDerDang 10y agoI like brew, but it's complete ignorance of OSX deployment target version (macosx-version-min) means it's useless for building software intended to run on machines other than the developer's. Most commercial software in other words. I realise that's outside of it's intended feature set, and it's fine for getting dependencies for other people's github projects or whatever. But what I'd really like is the ability to get dependencies that I can feed into my CI system to build software I intend to give to end users.
- rvalue 10y agoI enjoyed working and using Homebrew. My first contribution was to bring python 3.5.1 to brew. Loved the processes they have in place for anyone to make a change and have it available for distribution for the whole world using brew on OSX. Great job for the brew maintainers and contributers. You guys make everyone's job a lot easy!
- zpallin 10y agoYesterday I was downloading a cask and homebrew told me to update because homebrew no longer needs to own /usr/local. I think that was a perfect way to be introduced to this release :)
- gmisra 10y agoIf Mike is still here in the comments, can you talk a little bit about versioning support? Is this something that's on the roadmap at all, or something that Homebrew has a strong opinion about? In general, it's a very useful (and pleasant to use!) tool - except for when trying to manage different versions of the same dependency on the same system. Since this is such a big deviation from most package managers, and feels intentional, I'd like to understand why, and whether there is a "homebrew way" of approaching multi-version management. Thanks again for all of your hard work!
- mikemcquaid 10y agoWe're working on it: https://github.com/Homebrew/brew/issues/620 https://github.com/Homebrew/brew/issues/620
- saynsedit 10y ago/usr/local was bad but /usr/local/Homebrew is worse. The best would have been /opt/brew (short, no uppercase letter)
- tnorthcutt 10y agoWhy is /usr/local/Homebrew bad?
- saynsedit 10y agoBecause the UNIX hierarchy is standardized. System admins only expect bin, lib, etc, share, etc. to be in /usr/local. Imagine deleting /usr/local with the intention of only deleting local packages and accidentally breaking a Homebrew install. Not to mention it's an uppercase H which breaks UNIX file name convention.
- deleted 10y ago[deleted]
- mrweasel 10y agoI've had few (minor) issues with Homebrew, so I've been wondering about pkgsrc. Has anyone tried using pkgsrc, as a replacement for Homebrew?
- eddieh 10y agoI found pkgsrc to to be pretty great, but some of the packages are organized in odd ways and badly named. For example TexLive isn't called texlive. Same with xorg-server. I also couldn't figure out how to install Mac specific variants of things like Emacs. So I'm not giving up MacPorts anytime soon.
- niahmiah 10y agoHomebrew used to be my go-to tool for installing packages... But now, with the new Docker for macOS, I never need home-brew anymore. It is especially helpful when you need to run 2 different versions of an app (like elastic search) for different projects. I can't see myself returning to Homebrew now. That is just not the way to do things anymore.
- kstrauser 10y agoApples and oranges. I brew install git, Emacs, jq, and other dev tools. Packaging stuff in Docker is fine, but first you have to create or fetch something to package.
- deleted 10y ago[deleted]
- thomnific 10y agoUgh, ugh, ugh. I just tried Homebrew for the third time the other day and it made a complete mess of my /usr/local/bin and also screwed up my install of rvm ... never again will I give it a chance. Sorry, but IMO Homebrew is crufty, opinionated software with poor separation of concerns. Macports is the (objectively?) better choice for my needs.
- Osmium 10y ago> it made a complete mess of my /usr/local/bin In that case you might be glad to hear that in v1.0.0: > Homebrew’s default repository installation location changed to /usr/local/Homebrew to keep your /usr/local cleaner Personally, I really like Homebrew and have never had problems (c.f. MacPorts which gave me big problems a few years ago), but I don't use /usr/local for much else, so that's probably why.
- thomnific 10y agoHeh, fair enough and thank you, good to know :) Maybe in another year or two my frustration will have abated somewhat. Don't get me wrong, I think it's great that the devs recognized using /usr/local/bin was a bad decision (even if they were kind of forced to because of Apple's SIP). However -- I just remember, when Homebrew was getting started, all the supercilious (dare I say arrogant?) advice in the docs ... oh, just install to /usr/local, "seriously", etc. (Looking for a reference in archive.org right now ...) Even their whole "Macports driving you to drink?" thing rubbed me the wrong way -- maybe I'm humour-deficient, but I think to criticize another project when your alternative isn't clearly better is just bad taste. That being said, I am genuinely curious: is there any one awesome thing is that Homebrew does that Macports can't do? Or better, what kind of problems arise from using Macports? I recognize that packaging in Ruby is probably more convenient than in TCL, but other than that? It seems to me that Homebrew is just getting closer to what Macports did (correctly) in the first place. The only way Macports has ever inconvenienced me is requiring a fresh install from time to time when Apple updates their OS, which (for my use case) is minor.
- eddieh 10y agoMacPorts isn't without problems, but I can't use Homebrew. Just the message that is printed when you `brew install texlive` is a deal breaker. I don't want to manage packages separately from my package manager, that's crazy and defeats the purpose of a package manager.
- crooked-v 10y agoAs a side note, Ansible users might be interested in the roles I've been putting together for a bunch of the apps I regularly use [1]. You can kinda use homebrew-bundle in place of some of this stuff, but even then there's random installs that need extra configuration or general mucking about with that homebrew-bundle doesn't give a good way to encapsulate (for example, see the duckdns-updater repo and the template it uses [2]). [1]: http://galaxy.ansible.com/icopp/ http://galaxy.ansible.com/icopp/ [2]: https://github.com/icopp/ansible-duckdns-updater https://github.com/icopp/ansible-duckdns-updater
- FatherShawn 10y agoHomebrew has been my "go to" package manager for years! Well done!!