5 ms·
It might be good to explain how this differs from zerobrew [0], which is trying to accomplish the same thing [0] https://github.com/lucasgelfond/zerobrew https
by luizfelberti 6mo ago
It might be good to explain how this differs from zerobrew [0], which is trying to accomplish the same thing
[0] https://github.com/lucasgelfond/zerobrew https://github.com/lucasgelfond/zerobrew
- zieka 6mo agoI also have a solution mostly for myself but others are welcomed to it: https://zieka.github.io/bru/ https://zieka.github.io/bru/ Outlined some differences here between the various projects; might be useful: https://github.com/zieka/bru?tab=readme-ov-file#how-bru-compares https://github.com/zieka/bru?tab=readme-ov-file#how-bru-comp...
- tomComb 6mo agoAnd zerobrew, like the original Homebrew, is compatible with Linux. It appears that Nanobrew is not. I care about the light-weight efficiency of these new native code variants much more when I want to use brew on some little Linux container or VM or CI, than I do for my macOS development machine.
- Alifatisk 6mo agoZerobrew looks mature, I'll check it out. Btw, I noted this: > Zerobrew is experimental. We recommend running it alongside Homebrew rather than as a replacement, and do not recommend purging homebrew and replacing it with zerobrew unless you are absolutely sure about the implications of doing so. So I guess its fine to run this alongside Homebrew and they don't conflict.
- phist_mcgee 6mo ago>Install zerobrew via brew as per the official instructions. >Immediately get an error saying the install path is too long and needs to be fixed as /opt/zerobrew/prefix is too many bytes. Yeah gonna need some work.