Use copr:// links for external repositories#11562
Conversation
|
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 |
|
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. |
ekohl
force-pushed
the
rpm/develop-better-chroots
branch
from
1ee34d4 to
70e16e2
Compare
|
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. |
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
force-pushed
the
rpm/develop-better-chroots
branch
from
70e16e2 to
ec92bd9
Compare
I can file that but, that is a further optimization. |
3 participants
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.