On 1/14/22 05:36, Neal Gompa wrote:
On Fri, Jan 14, 2022 at 7:27 AM Leon Fauster via epel-devel <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:Am 14.01.22 um 13:02 schrieb Josh Boyer:A fairly accurate list of packages removed in RHEL 9 can be found in our RHEL 9 Adoption documentation: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html-single/considerations_in_adopting_rhel_9/index#removed-packages_assembly_changes-to-packagesIt seems that RH does not see RHEL as workstation OS anymore. Many tools were/will be removed. I do not need to be bright to anticipate that in the future (e.g. RHEL11) the trouble will prevails the benefit. EPEL QA is better then ever but it will not fill the gap. Thats like swimming agains the stream. Unless RH incorporates EPEL into his strategies. Like keeping the volume of packages officially and just shifting the borders ... thought.I think that's an unfair characterization. While it's certainly true that RHEL focuses on server workloads (it's easily an order of magnitude more sales than workstation ones), it's also true that Red Hat is *finally* investing in EPEL. This is the *first* RHEL release where Red Hat is *directly* investing in helping the community bring up EPEL. The RHEL folks are giving us a path to request packages as needed from being buildroot-only (thus internal to non-public RHEL Koji) to published repositories (thus usable by EPEL and third-parties). I *personally* have done this now many times with great success, and the consequence of that is we're able to get content into EPEL faster than ever before. We're even going to be ready for the RHEL 9.0 GA, which is something we've never had before.
I seem to have missed how to do this, could you point me to the right process?
Thanks! -- Orion Poplawski he/him/his - surely the least important thing about me Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 https://www.nwra.com/
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
