[EPEL-devel] Re: Modules for EPEL9

[Kevin Fenzi]

On Thu, Mar 24, 2022 at 07:09:33PM -0400, Neal Gompa wrote:
>  On Thu, Mar 24, 2022 at 6:38 PM Kevin Fenzi <kevin(a)scrye.com&gt;
> wrote:
>  >
>  > On Thu, Mar 24, 2022 at 07:56:15AM -0700, Troy Dawson wrote:
>  > > It was talked about December 2021, and pushed off to the new year.
>  > > https://pagure.io/epel/issue/135
>  > > It's the new year, and you are the first this year to ask for it.  So,
> time
>  > > to get it back in the discussions.
>  > > Could you please put what modules you want to build in that ticket, so we
>  > > can help prioritize it.
>  >
>  > Personally, I'd be happy just not doing modules at all for epel9 given
>  > the limitations we have (cannot build any module that requires rhel
>  > modules). I'd prefer we have folks just use compatiblity packages
>  > instead.
>  >
>  
>  What's stopping us from being able to depend on RHEL modules? Koji now
>  supports enabling module streams on a per tag basis, so it *should* be
>  possible now. 
As far as I know, MBS has no way of handling this case. 

It only knows about modules it itself has built, it doesn't have a way
to tag in an externally built RHEL module to be used as a BuildRequires
for another module. 

https://pagure.io/fm-orchestrator/issue/1653

kevin