On Mon, Jan 31, 2022 at 06:48:21PM +0000, Gary Buhrmaster wrote: > On Mon, Jan 31, 2022 at 4:55 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > > The limited arch policy we had for epel7 had a number of problems. > > At first we just said 'rebuild the exact rhel version' and then we > > switched to 'add a 0 to release so the rhel package always gets > > installed in favor of it'. > > It (probably?) would not hurt to have the epel > repos have a higher cost in the repo config > to discourage choosing the epel package over > the rhel package (if all things are equal, but > of course, they are not always equal). > > For some specific cases where I needed to > build the -devel package in a copr (until or > unless I can get the -devel packages shipped > in CRB (or equivalent)) I have manually set > the cost for the copr repos to be high so that > for a non -devel install I got the rhel versions. > I would love to know if there is a better way. > It all just seems so non-optimal. Sure, we could do that, but it's far from foolproof. Many people make their own repo files, or they might have their own weight schemes. It also doesn't help any building against things in koji. kevin
Attachment:
signature.asc
Description: PGP 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