On Tue, Nov 23, 2021, at 4:28 PM, James Cassell wrote:
Will things be slower than native ostree?
The only thing that will be less efficient is wire transfer as of right now. But
we're going to be working on that.
I've got no problem with the capability being added, but I do
wonder,
Why not rojig, aka native RPMs plus a special metadata RPM, aka jigdo
for ostree?
Ah yes. I spent like 2 solid months working on all that only to have it not actually be
used...
So backing up a level, really the question is: What is the "center of gravity"?
Is it rpms, or ostree, or containers? This Change isn't answering that question
decisively, but it is a large move closer to OCI/Docker containers.
We've already got great RPM infrastructure. Plus we could
get rid of countme.timer and instead ride the rpm-md connection like
the RPM-based variants do.
Mmm, I don't see a big problem with having a distinct rpm-ostree-countme.timer,
it's not a lot of code.
But your reply is so far skipping over really the biggest change: making it a first class
operation to build *derived* images using any Docker/OCI build system. For a lot of
people that will be Dockerfile, but if you follow the CoreOS proposal we are actively
discussing a more declarative/intelligent frontend.