On Sat, Sep 02, 2006 at 02:28:39PM +0300, Ioannis Vranos wrote:
> Axel Thimm wrote:
> >this is strongly discouraged by 3rd party repos. Selective/partial
> >enabling leads to some packages being updated, but not their
> >dependencies, as the users would have to put all dependencies into
> >their filtering effectively replicating a depsolver's work. Also
> >dependencies change over time and therefore break any filtering.
> >
> >The often made recommendation to filter repos leads to worse bugs as
> >they become dependent on the personal filtering thus every user has
> >his own set of bugs and any support attempt is futile. A typical
> >example is that users filter with include=foo and libfoo is never
> >updated along ...
> >
> >I can only speak for ATrpms authoritatively, but I know the other
> >repos share the same opinion: Either use a repo unfiltered, or not at
> >all. If you start filtering things, you're on your own, please don't
> >even consider reporting resulting bugs.
> 
> 
> Usually, when I search and install an application from some third party 
> repository, I have all the repositories enabled in yumex. Until now I had 
>  no problems.
> 
> 
> Also, I expect each repository to provide all the dependencies of every 
> application it provides. Isn't this true?

It is. I was referring to setting up the system to not allow the repo
to fulfill all the dependencies properly. For example if you have
include/exclude filtering or temporarily enable a repo, explicitly
install foo w/o allowing a proper upgrade and thus missing for example
libfoo updates.
-- 
Axel.Thimm at ATrpms.net