consider folding into github.com/containers/bootc

[cgwalters]

This project was designed to be distribution independent; that's in theory. In practice today it is tied to both ostree and rpm (though the rpm part is definitely written in an attempted-to-be pluggable way).

But I think it will make more sense to fold this into https://github.com/containers/bootc - we're not going to have non-ostree support anytime soon, and if we do it should work in the same way as bootc. Also, I think we want bootc bootloader update e.g.

Also, the two projects are similarly named and it will be less confusing to just have bootc, not bootc and bootupd.

[dbnicholson]

FWIW, I'm hoping to start using bootupd in Endless OS and I doubt we're going to move to OCI payloads any time in the near future. Not to say that you can't do this or there's not value in unifying there. We'd probably just fork the existing code and carry on with it in that case.

[cgwalters]

and I doubt we're going to move to OCI payloads any time in the near future.

BTW, I'd love to chat about this with you at some point! Or maybe you can just write up at least briefly here why not or what the blockers/problems you see are?

[jmarrero]

I have no issue with this, the only hangup up I could see is how we do messaging about bootc being about doing one thing and doing that thing well (deployments).

I guess the bootloader is part of the deployment so...

bootc manages your deployments including the bootloader, using the container as the source of truth maybe is enough.