On Fri, 6 Sep 2024, Stephen Smoogen wrote:
On Tue, 3 Sept 2024 at 23:47, Carl George <carl@xxxxxxxxxx> wrote:
On Tue, Sep 3, 2024 at 1:16 PM Leon Fauster via epel-devel
<epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I wonder if RHEL10 will have a Workstation flavor? Or if CS10 will be
usable as Workstation OS. When I see all the missing/removed parts.
Can not imagine that EPEL can compensate this all (e.g. is firefox in
the compose?).
Why can't EPEL compensate for this? If RHEL doesn't ship it, then
it's probably eligible to be shipped in EPEL. Several desktop apps
such as firefox were dropped, but all it takes is someone willing to
maintain them in EPEL 10. If there is a package you rely on that was
dropped, then become a packager and file a bug asking the Fedora
maintainer to add you as a co-maintainer.
Going from my experience with trying to maintain out-of-tree Firefox's in
the past.. it is not something I would say is well suited without a lot of
dedicated resources. I am guessing that is the reason it is being pulled
out as some sort of flatpak or similar tool.
Mozilla has started shipping a firefox.deb for Ubuntu (and possibly Debian)
to compensate for Ubuntu moving to a Firefox snap.
I wonder whether they would take on RHEL10 ?
1. You need to keep rust and other tooling up-to-date. Easy to do early in
a RHEL release, but over time getting harder and harder. The CentOS-7
Firefox package needed a LOT of newer compilers, toolkits etc which then
needed even more tooling which had to be researched every update.
2. You need to keep up-to-date with what is an 'important' update and what
isn't. Firefox in Fedora may get updated fairly regularly to keep up with
mainline LTS, but the RHEL one may not because various fixes are low and
probably affected some testing.
3. You end up having to deal with a LOT and I mean a lot of consumer
complaints because some websites no longer work after an update which you
have no control over. They may have dozens of extras installed which now
don't work, or they may have a corrupt cache, or a dozen other things which
they expect the maintainer to fix.
I wish anyone signing up to do this good luck, but I would really say that
this may be something not wanted.
--
Andrew C. Aitchison Kendal, UK
andrew@xxxxxxxxxxxxxxx
--
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue