RPM Community Forums

Mailing List Message of <rpm-devel>

Using rpmdeps -v --perl

From: Jeff Johnson <n3npq@mac.com>
Date: Sun 07 Oct 2007 - 18:41:14 CEST
Message-Id: <43F1C8BE-2BCA-4289-99F2-A4E9768E6F53@mac.com>
Subdividing distro-wide dependency closure checking into
indepdendently verififiable per-component closure checks
is the only way out of (the soon to be a registered trademark ;-) rpm
    Dependency Hell


There are some additional changes that are going to
be needed for, say, perl. At the moment, the perl dependency
extractors emit several types of dependencies.

E.g. A quick check on whatever crapola I happen to have installed
indicates that these "perl" dependencies
      0  Requires: /usr/share/openldap/migration/migrate_common.ph
      1  Requires: perl >= 0:5.001
      2  Requires: perl >= 0:5.002
      3  Requires: perl >= 0:5.003
      4  Requires: perl >= 0:5.004
      5  Requires: perl >= 0:5.005
      6  Requires: perl >= 0:5.006
      7  Requires: perl >= 0:5.006001
      8  Requires: perl >= 0:5.006_000
      9  Requires: perl >= 1:5
     10  Requires: perl >= 1:5.0
     11  Requires: perl >= 1:5.8.0
are not in a "perl(...)" name space. The first entry is a file  
dependency,
the other dependencies are package, not "perl(...)", dependencies,
and so are generated as false negatives when using
     /usr/lib/rpm/rpmdeps -v --perl

Getting all the data assigned to specific name spaces
is a necessary precursor to checking partial dependency closure  
independently
of distro-wide closure.

Or just complain about "dependency hell" (tm) ...

73 de Jeff
Received on Sun Oct 7 18:41:34 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.