On 01/10/2014 02:47 AM, Manuel Wolfshant wrote:
On 01/10/2014 03:31 AM, Ljubomir Ljubojevic wrote:
On 01/10/2014 02:18 AM, Manuel Wolfshant wrote:
On 01/10/2014 01:24 AM, Ljubomir Ljubojevic wrote:
- yum-plugin-priorities should become mandatory for all CentOS Variants
including Base distro.
[..]
IActually a saner and less prone to surprises approach is to rely on exclude= and includepkgs=
Try to explain that to a 50-year old woman that only wants to listen to her MP3 collection ;-)
I guess I did not explain my idea well enough.
I am not opposed in any way in including references to the needed 3party repos and by matter of consequence, 3rd party packages. What I am trying to say is that instead of relying on priorities which are very often creating issues ( the conflicts between EPEL and rpmforge being notorious ) , you should rely on the exclude/includepkgs system and fetch exactly the packages that you need and make sure nothing else gets downloaded/included/installed.
I have my own repository for last 5-6 years with mirrors of all major repositories and few separated repositories with downloaded, compiled, test, etc. packages. I have used exclude= but it is not as flexible as creating separate repository with only selected packages from other repos. At various times packages from different repositories might be used. My choice was to set priority of EPEL higher then RepoForge, so every duplicated package was only used from EPEL, and I could still use any other Repoforge package. It is same with my own repo, I gave it a highest priority. All I need to do to add new package to my repo and it will automatically be used in stead of package in repositories with lower priorities. No need to edit .repo file of every user for every new packet added.
My line of thinking is that every SiG will create it's own repository (or more) and with repositories with priorities all they need to do ever is to put needed packages in repository and users only to install the package.