Re: Thoughts: epel-release auto-enable crb repo

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

 





On Thu, Jun 16, 2022 at 10:22 PM Carl George <carl@xxxxxxxxxx> wrote:
On Wed, Jun 15, 2022 at 5:12 PM Troy Dawson <tdawson@xxxxxxxxxx> wrote:
>
> I'm totally top-posting, and I apologize for that.
>
> For right now, I'm going to put my enable-crb script in epel-release, but not automatically run it in a %post script or anything.
> The debate about putting it in a post script, or a separate package, can go on independently of the script.
>
> This does a few things.
> - give people a single, easy to remember way to enable crb
> -- Right now if you install anything but RHEL you might remember "dnf install epel-release" but then you forget what the dnf command is to enable a repo, and you might forget if it's crb or powertools.
> -- It will make scripting easier because you just have one command that will work across all RHEL compatibles.
>
> - gives the script a chance to find all the corner cases
> -- It's worked on everything I've tried thus far, but I'm sure there are some corner cases or two where the script doesn't work.
>
> I was thinking of it being
>   /usr/bin/enable-crb
>   /usr/bin/epel-enable-crb (a link to enable-crb)
>
> Thoughts?
>
> Troy
>
I think it would be nice to be able to both enable and disable from
the same script.  This would come in handy when you are looking for
things that don't install when crb is disabled.  I don't see anything
else in Fedora or RHEL that ships a command with the name crb, so how
about that?

crb enable
crb disable

That shouldn't be too hard.  I'm going to give it a shot.
If that takes too long, I'll just push what I currently have for now.

I notice that you said crb-enable, crb-disable.
Do you like having the name first, or the function first?

enable-crb vs crb-enable  ?

either way I want to have it by itself, as well as starting with epel

epel-enable-crb  vs epel-crb-enable  ?

Troy



_______________________________________________
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

[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