On Wed, 2007-09-05 at 00:36 -0400, James Antill wrote:

> 1. I want to enable an acroread/picasa/whatever specific repo. but I
> _probably_ don't want that repo. feeding me their glibc update or
> something else outside of that specific application.

we have a mechanism for that, though: includepkgs=list of apps here

and then only those pkgs are included from that repo.


> 2. I want to enable a third party repo. which has newer versions of one
> or more applications, firefox; postgresql; fish; whatever (including
> python/yum/whatever that could be in "base").
>  Here a subset of "newer" also means things like gxine/totem with
> non-US-free codec support.
> 
> ...and while it's possible that #1 can be solved by repo. level
> priorities, or protect base type stuff, #2 isn't helped at all.
>  Currently I manage by using disabling the "lower priority repo." and
> whenever I want specific things from it using --enablerepo=blah, which
> if we want to make easier to use for everyone would have something like
> the following properties:
> 
>  i. yum update -- doesn't take any newer packages from the special repo.
> that aren't from that repo. and _optionally_ doesn't take any newer
> packages from the normal repos. that are from the special repo.
> 
>  ii. yum update  foo
>      yum install foo -- takes foo from the special repo., if available
> and newer, but if foo has any required deps. from that repo. it would
> ideally warn about them, install them, but then when updates are
> available in the "normal" repos. move back to that version.
> 
> ...from what I know some of those properties are significantly hard to
> do atm. though, but I think that's roughly what people want :).

ugh. Number 2 of this translates roughly into: "Magically figure out
what I really wanted in my heart of hearts"


> > simple-local-repo-priority - allows you to setup a local repo that has
> > SOME of the pkgs from another repo and know that the ones in the local
> > (or better priority repo) will be used. This only works for nevra-exact
> > pkgs from one to the other. This is useful for anaconda, mock, mash, etc
> > to let it know to use a closer copy of some of the files rather than a
> > remote one.
> 
>  If I understand this correctly, this is just a way of saying repo. X is
> faster than repo. Y ... I don't think you want to confuse that feature
> with priorities (although that would be a nice feature too :).

It is a bit like that, yes. So if everything else is equal use the
cheaper one.

-sv


_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

Reply via email to