Sourcing of third party RPMs

[castrojo]

Kyle helped us set up a ublue-os COPR where we can put stuff, and some of the images are pulling from RPMFusion, etc. We don't really have policy around third party repos but we should probably start talking about that.

This is all working ok for now, but long term we should just use the packages feature here for stuff when we can and just build them with actions.

[mitchejj]

I'm personally not a fan of the idea of adding xone or xpadeno but I did reconize the thrid party repo as a known eninity. While the Ubuntu build, and what I assume its replacement Bluefin, both use Tailscale.

I think it is important to declere if any repos are used outsdie of the defualts; and how a set standard on how those are added the the build. The main build script seems to be a perfectly fine way to do it, one block with everything listed and nothing else happening in that code block.

[castrojo]

Yea, we need to make sure the end user can trace and know exactly what's on the image.

[castrojo]

Quick note from an impromptu postmortem on the build failures. New 6.3.1 kernel needed a fix for xone to build, which was committed upstream 2 weeks ago but xone never released a new version, so negativo didn't pick it up because they're packaging the latest upstream. That caused the failure which led to main also not building.

For akmods we might consider just building them in our copr to remove a 3rd party dep, but also do git builds so we can rev faster if need be, and then we just need to decide if we gate in the build step or the rpm step.

[bigpod98]

Main will stay relativly faithful to upstream. While adding QoL additions to make life easier for general user