Understanding Prioritization

[Eli Wapniarski]

> > > Any additional insight relative to the FAQ would be very very much
> > > appreciated.
> 
> The behaviour I'm expecting, is one of exclusion. In apt, if I set a
> priority of a repository to 999 then that repository has exclusive
> priority over all other repositories that I'm using. 998 has the next
> priority in that any package from the repo given the priority of 999
> will not be superceeded by the 998 repository, but it will supercede
> anything given a lower priority, even if it means downgrading. The
> thing
> is, that repos build packages that occaisionally depend on packages
> that
> they themselves have built to enable certain features. Features that
> another repo may or may not include. A good example of this is the
> relationship between kde-redhat's repo and Fedora's repo. The next
> repo
> that I want to have priority of Fedora's is Freshrpms; especially over
> Fedora extras for the same reasons.
> 
> So essentially, the behavior that I've come to expect and love with
> priorities specified would be
> 
> 1) kde-redhat (999) - Exclusively takes precedence over everything
> else.
> Don't let anything else replace any file coming from the kde-redhat
>                                           repo.
> 2) Freshrpms (998) - Takes precedence over everything other than
> kde-redhat
> 3) everything below that is left at default.
> 

Actually, the only real improvement that I can think of to this behavior
is that if a repo decides to remove a package then smart should
automatically install the package next on the priority list; informing,
of course the reason being that the package has been removed.

Eli