xyny
xyny
That is similar to what I laid out as _the other way to solve building multiple similar images_ alongside modules. Could be interesting. I don't see the practical difference from...
> though with having the full recipe we probably don't need to push both images Is there any point in this if both images aren't pushed?
If `basic` is not published, that is essentially the same as doing `from-file` from a file that contains multiple module definitions (AFAIK totally supported, as should be doing the same...
> Ok so trying this out, it would seem that although GHAs support using truecolor, Gitlab CI doesn't and makes it look weird. So I'm going to try using standard...
Sounds like `rebase` and `upgrade` could be merged with an `rpm-ostree status` check, right? And `--push` being an arg and `rebase` being a subcommand doesn't make entire sense to me....
How about renaming `template` to `generate`, as that verb is commonly used in our docs and makes sense for what it's doing. I'm still for merging `rebase` and `upgrade` into...
The rebase option? I think `--push` and `--rebase` rhyme better. If we don't want to use the "rebase" term, I guess `--switch` would be the correct choice (per `bootc switch`...
I think it should be possible to make the build command fail if any of those incompatible parameters are defined at once.
I don't like the `install` and `replace` command/flag names. I think it should be either `rebase` per `rpm-ostree rebase` or `switch` per `bootc switch`. I also think the build and...
That sounds good!