Hi folks, I'm trying to sort the plugins we have which do something like providing package or repo priorities:
priorities - used like a super-epoch - any package in a repo with the better priority is kept, all others are excluded protectbase - any of the packages in a repo marked as base are kept, anything in add-on repo that updates/overrides base is excluded simple-local-repo-priority - allows you to setup a local repo that has SOME of the pkgs from another repo and know that the ones in the local (or better priority repo) will be used. This only works for nevra-exact pkgs from one to the other. This is useful for anaconda, mock, mash, etc to let it know to use a closer copy of some of the files rather than a remote one. So, the question is - if we brought a priority plugin into the core functionality - which of the above would make sense to implement? I'm listening to opinions though I already have some strong ones of my own. -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
