4 ms·
> It’s only happened twice in more than a decade, but I still have the feeling that I was better off compiling stuff manually and cultivating a tidy /usr/local/
by FnuGk 4y ago
> It’s only happened twice in more than a decade, but I still have the feeling that I was better off compiling stuff manually and cultivating a tidy /usr/local/bin like I did in early 2000s. But it’s probably rose-colored glasses and I’d definitively never take the time these days.
thats exactly what homebrew does.
- justinclift 4y agoA lot of Homebrew packages are pre-compiled binaries ("bottles" produced by Homebrew) that are pretty much just downloaded and untarred onto your system. The Homebrew formulas' are what's used to produce those binaries, or - if there's no pre-compiled one available - that's when it's compiled live on your system. Seems like a decent tradeoff, as otherwise installing (say) Qt could take an hour+, since that's a bit of a monster to compile. :)
- kimi 4y agoThe problem is that every time you install something it will update a gazillion dependencies because there is a minor version difference in a library I don't even use. And of course I did not ask for those binaries to be upgraded. When I do a yum install, 99% of the cases it just add the package I need. And won't mess with my dev tools.
- onedr0p 4y agoI believe you need to set the envvar HOMEBREW_NO_AUTO_UPDATE to avoid that problem.
- mdaniel 4y agoI always encourage folks to read over the environment section of the manpage, as it's extremely helpful: https://docs.brew.sh/Manpage#environment https://docs.brew.sh/Manpage#environment
- tambourine_man 4y agoSane defaults are important tough.