This has a bug... As Ryan noted, we want to behave exactly as we do now if all priorities are equal. In particular, we want to pay attention to pkgpolicy. In fact, "pkgpolicy=latest" should probably override repo priority completely. So the whole last paragraph of my pseudo-code (the paragraph that picks the one-true package out of all candidate versions in all the enabled repos) has to be completely re-thought. It's late and my brain hurts. I'll think about it in the morning! Rick On Saturday, August 2, 2003, at 04:21 AM, Rick Thomas wrote: > > Some psuedo-code... > >> For each repo section in the config file (in order): >> >> For each line in that repo section (in order): >> >> If line is "includeonly": >> For each package (in the repo) that matches a pattern >> on the "includeonly" line: >> Mark that package included. >> Mark that package not excluded. >> For each package in the repo: >> Mark that package excluded unless it is already marked included. >> >> If line is "exclude": >> For each package (in the repo) that matches a pattern >> on the "exclude" line: >> Mark that package excluded. >> Mark that package not included. >> >> For each non-disabled repo in the config file in priority order >> (worst first and best last): >> For each package (in that repo) not marked excluded (in >> version order -- latest version last): >> Mark that package picked. >> Mark all other versions of the same package in all repos >> (including this one) as not picked, overriding previous "picked" >> status if necessary. > > > Would this work? > > > Rick >
