seth vidal wrote: > On Sun, 2004-11-14 at 17:41 +0000, Max Bowsher wrote: >> In FC2, I used to use DAG and ATrpms for a few additional packages. >> Setting >> pkgpolicy=last and giving the additional repositories ids prefixed with >> 00 >> allowed me to easily get 3rd party packages when no official package >> existed, but without receiving 3rd-party updates to packages for which an >> official package exists. >> >> Is there any way to accomplish this with yum-2.1.x and FC3, now that the >> pkgpolicy feature has gotten lost in the grand 2.1 restructuring? >> > > pkgpolicy=last did get removed, you're right. It was not terribly > reliable when it came to packages being a higher revision in repository > above. So your goals would be thwarted. > ex: > 00repo has foo-1.1-1.noarch.rpm > > dag has foo-1.2-1.noarch.rpm > > you have foo-1.0-1.noarch.rpm installed > > now even with pkgpolicy=last you were still going to get the foo from > dag's repo not from 00repo. That is what I would want. (In my setup, dag is 00dag, and the only not 00 ones are the official base & updates). > in yum 2.1.12 (soon to be released) I've included a new option in the > config file: > > includepkgs= > > it's the opposite of exclude in a [repo] section. It lets you say you > want only certain packages from a repo rather than having to exclude the > ones you don't want. What if includepkgs=foo, but foo depends on bar, baz, quux? Would I have to manually enumerate all the dependencies of foo, and include them in the includepkgs statement? In any case, that doesn't help when I want a new package - I still have to go research which repository it is in, and add an include. Any chance of some means of assigning priority levels to repositories returning in a future release? Max.
