On Wed, Oct 6, 2021 at 3:36 PM Troy Dawson <tdawson@redhat.com> wrote:
>
> *this is worth a discussion in todays EPEL Steering Committee Meeting*
>
> It sounds like the epel9-next is going to startup by building against the CS buildroot. Changing it at this time would cause a delay.
>
> Thus we need to write some "verify build deps are released" checker. I have an idea of how to do this, so I'm willing to volunteer to write and run something.
>
> But, it would be good to have some discussion to determine if we want to keep using the CS buildroot for epel9-next, always. Or if we want to use it just as a bootstrap mechanism, and then switch to building just off the available CentOS Stream repos at some point.
>
> Thoughts?
> Should we always use buildroot? Or just keep up until we're fairly stable?
>
We should only use the buildroot repo for as long as we need to. The
*sooner* we can switch to the published content, the better.
This was discussed at the EPEL Steering Committee meeting. Here is the summary.
Someone correct me if I'm wrong.
epel9-next:
- starts off building off CS buildroot
- I will write a "check if all build packages are in the normal repos" checker, called "will it build" [1]
epel9:
- Use normal RHEL 9 repos (AppStream, BaseOS, CRB)
Checks/Tests/Future: (It's a little fuzzy on the timing of these)
- grobisplitter
-- see if we really need to use grobisplitter
-- I'm a little fuzzy on how or when we are going to test this
- "will it build"
-- After a period of time, check and see if we are happy with the combination of CS buildroot + "will it build" ?
--- Yes - determine if we want to keep it like this even after epel9
--- No - determine when the best/safest time to switch to normal repos
Troy
[1] - I plan on integrating "will it build" with a "will it install" checker. It will be called "will it" or "willit". I'm sorta excited about doing this. It's something I've wanted to do for a long time and I think I've finally got it figured out.