On Tue, 15 Dec 2020 at 10:45, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
On Tue, Dec 15, 2020 at 08:30:21AM -0500, Stephen John Smoogen wrote:
> Honestly I don't know how to deal with regular EPEL-8 development after
> this. EPEL is going to add an epel-next which they would ask for additional
> targets in mock for. However that does not fix building against the regular
> EPEL-8 target. I expect it will depend on what programs come up for
> development in the coming year and if the new -devel RHEL UBI images can be
> used for mock.
Or just the no-cost RHEL developer subscription? It seems like this is a
good use case for that, if it could be made easy enough that it isn't
painful for EPEL packagers.
Currently a mock -r epel-8 can be done on a EL7/EL8 and any active Fedora. It does not need any passwords or config setup.. just run a command. The developer subscription requires additional setup to point to the EPEL config to the access.redhat.com servers and similar things. It is easier to point the configs to the Springdale or similar repos.
This may change sometime in the future..
--
Stephen J Smoogen.
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
