Re: proposal: EPEL 8 Next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Holy name bikeshedding Batman!  To adddress all the naming comments
collectively, I am also of the opinion that "stream" is an overloaded term.
Can you tell someone with a straight face to install a package from a module
stream from the AppStream repo on CentOS Stream?  Not to be confused with
the appstream-data package that is also in the AppStream repo but isn't part
of a module stream.  I wouldn't be surprised by any entity currently using
"stream" in their name moving away from it in the future for clarity.
"Next" correctly describes the purpose of the repository, which is providing
packages compatible with the next minor release of RHEL.  That works for
CentOS Stream, RHEL Betas, and RHEL during the CentOS Linux rebuild gap.

On Wed, Sep 9, 2020 at 12:17 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote:
>
> On Wed, Sep 9, 2020 at 12:59 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> >
> > I'm a bit confused here... you seem to be conflating epel and this
> > epel-stream/epel-next. Do you mean both of them?
>
> Yeah, I'm thinking both. From a high level, I don't see them as being
> distinct, just different targets for the same idea. Of course, that
> doesn't mean there aren't lower-level issues that would make it hard
> or impossible. It's also possible that I'm just totally wrong; I've
> been a little under quota on that lately, so I'm due. :-)
>
> > would move over? We would need at least shared git (is that still
> > something that might happen someday?)
> >
> "In the fullness of time", as they say, that's something that might
> happen. Is that before the heat death of the universe? I can't say.
>
> I won't continue distracting the thread with this idea for now, I just
> tossed it out as an idle thought. But the naming suggestions are
> sincere.
>
> --
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis
> _______________________________________________
> 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



-- 
Carl George
_______________________________________________
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




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux