> being pushed as the 'best' alternative. > initially added that caveat section, after seeing priorities > self-induced dependency hell, and CentOS is blamed for it in > 'priorities' falls over and dies at that point from This particular page from a thread called " What's wrong with yum-priorities?" piles on my concerns: It could just be that it reminds me of apt 'pinning' and that makes me want to hurl. There are so many things about priorities that make me cringe all over. Gosh, I hope people do not set up yum priorities. Note: The upstream maintainer of yum, Seth Vidal, had the following to say about 'yum priorities' in September 2009: At the bottom of the Priorities page there is this very troubling disclaimer: The third suggestion is to use the Priorities plugin, which as I understand is actually built into DNF on CentOS 8. How do I know which packages should be excluded or included and when? Is this suggestion saying I should carefully study a third party repository before installing packages from it? I'm not opposed to learning the ins and outs of yum and dnf, but it would be terribly useful to map out a basic useful strategy for new users to get their feet wet with this approach. The second suggestion is to "use the exclude= and includepkgs= options on a per sub-archive basis, in the matching. The first suggestion is essentially to disable the EPEL and other third party repositories and then use something like this to install packages: ~]$ sudo dnf -enablerepo=epel install p7zipĭoes the above guarantee that some core part of CentOS will not be overwritten (the documentation vaguely implies that the problem is related to updates and not necessarily installing packages)? If so, does that even help? What happens when you need to update the packages from third party repositories? The yum Priorities plug-in can prevent a 3rd party repository from replacing base packages, or prevent base/updates from replacing a 3rd party package. conf file found in /etc// See: man yum.conf See: man yumĪnother approach is to use the exclude= and includepkgs= options on a per sub-archive basis, in the matching. One approach is to only enable these archives from time to time, and generally leave them disabled. NOTE: If you are considering using a 3rd Party Repository, then you should seriously consider how to prevent unintended 'updates' from these side archives from over-writing some core part of CentOS. Here is the preceding section from the Repositories page for CentOS that sums up the problem and makes three suggestions about how that problem might be solved: It's almost like the CentOS documentation is saying "things should be OK if you use the EPEL- but who knows, something really bad could happen too, especially around point releases". I have empathized the phrase " should not". Enabling epel-testing on production systems is not a good idea. If you are willing to help test EPEL updates before they are pushed to stable, you can enable the epel-testing repository on your development/testing servers. Support available on Freenode in #epel, on mailing lists, and its issue tracker. The epel-release package is included in the CentOS Extras repository that is enabled by default. You can install EPEL by running yum -enablerepo=extras install epel-release. Packages should not replace base, although there have been issues around point releases in the past. Here is a section from the Repositories page for CentOS regarding the EPEL specifically:Įxtra Packages for Enterprise Linux (EPEL) - (See ) provides rebuilds of Fedora packages for EL6 and EL7. There is a lot of fear, uncertainty and doubt when it comes to using CentOS third party repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |