Thanks for the work to get us here! But I have some reservations/questions...

Why are we targeting tier-0 as the starting point?

The idea behind tier-x was to create a common starting point for IoT, Atomic Desktops, CoreOS.

https://gitlab.com/fedora/bootc/base-images/-/merge_requests/48

And we should be trying to use git submodules so we don't have to independently track changes to the upstream, right?

Thanks for the work to get us here! But I have some reservations/questions...

Why are we targeting tier-0 as the starting point?

I wanted to test the changes in Rawhide before enabling them in F41.

The idea behind tier-x was to create a common starting point for IoT, Atomic Desktops, CoreOS.

https://gitlab.com/fedora/bootc/base-images/-/merge_requests/48

Tier-x is not available in Fedora 41 and is targeted for Fedora 42.

And we should be trying to use git submodules so we don't have to independently track changes to the upstream, right?

Agreed. Once everything is working in Fedora 41 I can move Rawhide over to submodules.

Thanks for the additional context.

I'm unconvinced that we shouldn't be trying to start this process with tier-x in Rawhide with git submodules. But if you feel you have a plan to get us there, I'm won't continue to argue.

Dropped grub2 from x86 packages listed in bootupd.yaml.

It pulled in grub2-pc, grub2-modules and which for BIOS support which we don't have in IoT.

And we should be trying to use git submodules so we don't have to independently track changes to the upstream, right?

submodules are also "special" and they're not always great, personally would prefer if upstream didn't use them

LGTM let's make this happen :)