Open jamescassell opened 4 years ago
More info on rojig: Let's link https://github.com/coreos/rpm-ostree/issues/1081
What would it take to have the pipeline (and/or koji) generate RPMs that represent each release?
I did some work on this for coreos-assembler here: https://github.com/coreos/coreos-assembler/pull/1003 as part of potentially using it for Silverblue.
The basic thing here is: As soon as package layering is involved, rojig becomes much more compelling.
But once container image deltas land, container images become a much saner way to ship the OS and obviously align with how we ship apps.
There are tons of tools and products that support mirroring, managing, and syncing yum repositories. Whether it's a local mirror for faster access, or a completely offline network, it's very useful to be able to download and automatically sync updates thru pre-existing processes.
rpm-ostree rojig
seems to allow this.What would it take to have the pipeline (and/or koji) generate RPMs that represent each release?