Re: How does yum decide rpm A to depnd on B?

On Tue, 2008-08-19 at 08:12 -0700, Ian Kaufman wrote:
> 
> 
> On Mon, Aug 18, 2008 at 6:32 AM, Yi Yang <[email protected]> wrote:
>         On Mon, 2008-08-18 at 12:56 -0400, Greg Ward wrote:
>         > On 18 August 2008, Yang, Yi Y said:
>         > > I notcied yum repo has a xml file primary.xml, that
>         provides what a rpm
>         > > requires and what a rpm provides, optionally, yum repo can
>         also have a
>         > > sqlite database primary.sqlite which has similar info to
>         primary.xml, I
>         > > want to decide dependency according to xml file or sqlite
>         database, my
>         > > decision logic is A requires B and C provides C, then A
>         depends on C, I
>         > > don't know if this logic is correct, I don't know how to
>         decide the real
>         > > dependency logic, anybody know it?
>         >
>         > As I understand it, the definitive source is the .rpm file
>         in the
>         > repository.  If you have direct repository access, just
>         query the file:
>         >
>         >   rpm -qp --depends A-<version>-<release>.<arch>.rpm
>         
>         --depends should be --requires.
>         
>         
>         >   rpm -qp --provides A-<version>-<release>.<arch>.rpm
>         >   ...etc...
>         
>         
>         These commands just output some components but not packages.
>         
>         Any command can give out all dependencies of one package?
>         
>         Does yum have such a feature?
>         
>         
>         
> 
> "yum deplist <package>"
> 
> will show all of the dependencies and what package provides them.
But if package A depends on B, B depends on C, can "yum deplist" show C?

My problem is if there is a yum command giving out all direct or
indirect dependencies, how does yum decide dependency?

> 
> Ian
> 
> 
>