Skip to content

Conversation

@ekohl
Copy link
Member

@ekohl ekohl commented Dec 6, 2024

This has the benefit that COPR internally knows where to download it from. We don't need to repeat the specific buildroot name.

My long term goal is to have less configuration for the buildroots so it becomes easier to manage multiple. Ideally we support multiple architectures with minimal configuration.

At this moment it's untested, but I'd like to experiment with this. In fact, we should probably use https://fedora-copr.github.io/posts/runtime-dependencies and enhance obal to manage that.

@ehelms
Copy link
Member

ehelms commented Dec 6, 2024

That blog post is unclear to me if it translates runtime dependencies into the buildroot dependencies. Or if it translates buildroot dependencies that same way when using copr:// -- have you been able to test this idea out on a repo?

@ekohl
Copy link
Member Author

ekohl commented Dec 6, 2024

No, I started to do that but it's the first time I used obal in a long time and immediately ran into theforeman/obsah#37 again. It's https://www.youtube.com/watch?v=AbSehcT19u0 all over again.

This allows COPR to figure out the exact download URLs. It also removes
some of the architecture specific naming and may allow defining external
repositories at the COPR project level instead of the chroot level.
@ekohl ekohl force-pushed the rpm/develop-better-chroots branch from 1ee34d4 to 70e16e2 Compare December 20, 2025 19:30
@ekohl ekohl marked this pull request as ready for review December 20, 2025 19:31
@ekohl ekohl requested a review from a team as a code owner December 20, 2025 19:31
@ekohl
Copy link
Member Author

ekohl commented Dec 20, 2025

I've validated this concept in https://community.theforeman.org/t/bootstrapping-foreman-rpm-packaging/45290. In #12872 it's a lot easier to use this, but rebuilding on ARM was actually way nicer.

The next level could be to define the external repos this way on the project itself instead of per buildroot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants