Re:Mcfly – neural-network powered directory and context-awar...
by staycoolboy on Wednesday July 08, 2020 @01:06PM
(#23771843)
It depends on the package.
Some folks want the newest and brew might update faster than Debian, e.g., Cmake was at 3.10 on Ubuntu for the longest time but Brew had it at 3.15.
Me personally, I've run into waaaaaaaaay too many issues trying to run more than one package manager. The best solution I've encountered: use the native package manager first, and if you need a new version of something, build it manually BUT SAVE THE BUILD DIRECTORY for uninstall.
(My favourite bug was autoconf tools requiring dependencies that were mixed between brew and macports: each one required the other to be first in the PATH!!)
Re:Mcfly – neural-network powered directory and context-awar...
by prashnts on Wednesday July 08, 2020 @12:29PM
(#23771458)
I tried LinuxBrew on my Raspberry Pi to install couple of packages not in Debian. Unlike MacOS, you don’t get « bottled » packages (pre-built), so it took a while to compile and pulled in build dependencies. Wasn’t pleased, but:
I would consider it for writing build/install recipes for personal projects since I’m familiar with it. So that’s at least one use case. :)
Re:Mcfly – neural-network powered directory and context-awar...
by gkfasdfasdf on Wednesday July 08, 2020 @12:39PM
(#23771570)
I use it in crostini on my chromebook. Packages are much newer than what comes with the debian install there. Also doesn't require root access (after installation of linuxbrew itself).
Can someone tell me why someone would want to use brew rather than their existing package manager on linux? Is it due to existing familiarity with brew, or the large number of snippets in people's docs that show how to install with brew?
Genuine question, I'm sure there are reasons to want to use it over a builtin package manager on linux, I'm just not sure what they are.