#1095 buildroot repo creation
Opened a year ago by kevin. Modified a year ago

Fesco has been discussing adding ursa-major in Fedora ( https://pagure.io/fesco/issue/2003 ).

This would allow configured modules to be available in the non modular/normal buildroot for packages. However, we still would like some way for users to download src.rpms and build them outside koji and get the same results as we do in koji. One thought for this would be for us to generate a 'buildroot repo' that we make and ship and users could use to populate their build env/mock and get similar results to we do in koji.

Ideally, this buildroot repo would just contain repodata and that repodata would just point to the already existing packages in the repos we already ship.

If thats not possible, it could just ship hardlinked copies of modules content that are used in the buildroot and users could enable Everything and buildroot to get the complete buildroot.

Since the buildroot changes, we probibly would want to generate this as part of rawhide every day, and for new releases we would generate it for GA and then for updates.

FESCo would like to know how feasable this might all be. Thoughts?


Ideally, this buildroot repo would just contain repodata and that repodata would just point to the already existing packages in the repos we already ship.

This is not possible. Pungi creates self-contained and standalone composes, and pointing to packages in another location goes contrary to that.

If thats not possible, it could just ship hardlinked copies of modules content that are used in the buildroot and users could enable Everything and buildroot to get the complete buildroot.

This means basically only creating a separate repo that would include only the modular additions, right?

The Koji buildroot consists of

  • non-modular packages – users would get these from Everything
  • a set of modules – users would get these from the new repo

This should be easily doable by adding a new variant to the compose, that would only include the required modules.

It could be part of regular Rawhide nightly compose, though it might be better to have it as a standalone compose. If it only contains a couple modules, it would have no connection to actual nightly, and would be fairly fast.

It might even be possible to use ODCS to create the modular buildroot additions repo, which could be used at least for testing.

Login to comment on this ticket.

Metadata