actually in line with #9 but uhh yeah
Some people still want local derivations of their system but they don't want to upload their custom image to a registry or whatever reason, so I propose a middle ground solution to the weird imperative workflow expectation by just keeping an OCI build context at like /etc/bootc-env/ or something, and having it be treated like a manifest of packages to install or whatever
like you do
and instead of it installing the package directly it writes to /env/bootc-env/manifest.toml and appends neovim to the package list in that file and you rebuild the image locally and rebase to it instead, like this
um env build
# builds to `localhost/um-image:latest` or something
um env update
# pulls upstream image declared in `/env/bootc-env/Containerfile` by doing `podman build --pull=newer ....` or something and then bootc update/rebase it
a persistent stateful layer is out of scope here, but with this we can provide a way to declare user derivations locally and tooling to easily set up and build them instead of expecting the user to deal with a persistent overlay that introduces state drift over time
actually in line with #9 but uhh yeah
Some people still want local derivations of their system but they don't want to upload their custom image to a registry or whatever reason, so I propose a middle ground solution to the weird imperative workflow expectation by just keeping an OCI build context at like
/etc/bootc-env/or something, and having it be treated like a manifest of packages to install or whateverlike you do
and instead of it installing the package directly it writes to
/env/bootc-env/manifest.tomland appendsneovimto the package list in that file and you rebuild the image locally and rebase to it instead, like thisa persistent stateful layer is out of scope here, but with this we can provide a way to declare user derivations locally and tooling to easily set up and build them instead of expecting the user to deal with a persistent overlay that introduces state drift over time