On Sun, Apr 25, 2004 at 10:44:45PM -0400, seth vidal wrote: > > One of the problem I'm facing using multiple repositories is that a > > number of them contain the same package, but with different > > dependencies or build options. This can sometimes lead to a package > > being installed/upgraded on my system when I don't want it. Often, I > > add a repository to my list only because I'm interested in one package > > in it. Alternatively, I may want to maintain my own yum repository of > > a custom-built package for my server farm, and I would want to ignore > > that package in all repositories except mine. The global "pkgpolicy" > > option is not flexible enough to allow such fine-tuning. > > then exclude the package in the other repos except for yours. Ok, that's reasonable. > > Could I request a feature called, for example, "include", which could > > be used on a per-repo basis, to only track a certain package(s) in a > > repository? I know this has some dependency-related issues (for > > example, the "included" package may depend on other packages in that > > same repo). Perhaps the include can be applied after the dependency > > checks. > > That's painful to code and maintain and of very little benefit. > > includeonly= in a repo is not unreasonable - it just inverts exclude= > the include keyword is already tied up in yum.conf for the future but > includeonly or includepkgs is not. That's also reasonable. Look forward to seeing this option in a future release of yum. -- Anand Buddhdev
