-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fully static build by default #51
Comments
Definitely interested in providing this sooner rather than later! It wouldn't be as easy as ..so one kinda interesting option would be to build Brioche normally in CI as a "stage 1" build, then to use Brioche itself to build Brioche as "stage 2", which would then be a self-contained package. I'll try to get an idea of how much effort that is to set up soon, to see if I could get it in as part of the next point release |
🤯 |
Following the v0.1.4 release, Brioche's packed builds should work on NixOS, Alpine Linux, and any other distros that don't use glibc! The packed builds work exactly as described above: they're builds of Brioche built with Brioche itself, so they're fully portable. Currently, the default is still to use the glibc-based builds, but the installer script will now try and detect if it's running on a system without glibc, and will automatically install packed build instead (see brioche-dev/brioche.dev#12 for more context). I'd still like to make packed builds the default longer-term, so I'm not closing this issue out quite yet. The remaining work is to support automatic updates for packed builds and to figure out how to migrate existing installations over. Also, I've only manually tested in Alpine via Docker, so I'd appreciate feedback if anyone tries out Brioche on an actual Alpine machine, or on NixOS or other distros that don't use glibc or the FHS! |
Trying out brioche on NixOS gives the expected result:
For the kind of tool brioche is, it seems that providing a fully statically-liked executable might be beneficial?
The text was updated successfully, but these errors were encountered: