i think the current implementation may start to give the idea of what is desired, but i was struggling with how to run fedora specific stuff in a container to get DNF/RPM info, but still have that be in a gitup action workflow step so we can use the results in metadata for building the image
I'll take a look at the existing implementation and see if I can't come up with something. First thing I noticed - why are workflow runs on PRs being disabled?
i don't know what you mean? we run workflows on PRs all the time, just not without approval for non-member/non-approver, and we don't push images to GHCR for PRs
yeah, i realized when i was looking at some bazzite stuff, "oh man! we could really benefit from having the proper kernels defined!" a lot of downstream stuff would be simplified as bazzite and bluefin wouldn't need variables to make matches or assumptions about the kernel version... but could query the image lable directly
No problem! I'll be out for about an hour in an hour and a half and for a couple hours this afternoon but other than that, my weekend is (so far) wide open
i expected to do a podman run/exec, and inside there, use dnf to query what kernel WOULD be installed given the build-args and env vars for the kernel flavor
If we want what would be installed, that completely changes implementation and I need to scrap this :/. We can easily get what is installed this way though...
i do think we need to find out what WILL BE installed before building the image, because we need to have the label defined in advance so we can use it in the build step
B
E
