Some users will want to pre-build fish for given platforms in a way that can be fetched directly instead of building from source and we will need some plumbing to support this. Will also need to ensure we're handling credentials for private artifact registries.
This is a bit complex today since Fish requires many runfiles and would need to be archived with them and configured to run correctly after unarchiving.
May be necessary to wrap the entire Fish environment as an executable archive. What does that solution look like? Build Fish, make a SquashFS from Bazel execroot, squash it into a rust binary with an include macro, and unpack/execute it at runtime?
Some users will want to pre-build fish for given platforms in a way that can be fetched directly instead of building from source and we will need some plumbing to support this. Will also need to ensure we're handling credentials for private artifact registries.
This is a bit complex today since Fish requires many runfiles and would need to be archived with them and configured to run correctly after unarchiving.
May be necessary to wrap the entire Fish environment as an executable archive. What does that solution look like? Build Fish, make a SquashFS from Bazel execroot, squash it into a rust binary with an
includemacro, and unpack/execute it at runtime?Is this more easily solved upstream?