summaryrefslogtreecommitdiffstats
path: root/cron-jobs/integrity-check
diff options
context:
space:
mode:
authorXavier Chantry <shiningxc@gmail.com>2009-08-28 01:27:12 +0200
committerAaron Griffin <aaronmgriffin@gmail.com>2009-08-28 18:08:25 +0200
commit620b631fedbbd3596baa6752b9234249a2239a2a (patch)
treef7980b94491bd0dfb89f0925dee123d8088d7397 /cron-jobs/integrity-check
parentd455a0b2cd72cd08b7b6cde878a29841f77a041e (diff)
downloaddbscripts-620b631fedbbd3596baa6752b9234249a2239a2a.tar.gz
dbscripts-620b631fedbbd3596baa6752b9234249a2239a2a.tar.xz
add deplist to hierarchy problems
This should help a lot figuring out whether a given hierarchy problem is fixable (if it doesn't require moving too many deps). example output core/crda depends on extra/python-m2crypto (27 extra (make)deps to pull) core/iputils depends on extra/opensp (29 extra (make)deps to pull) core/iputils depends on extra/libxslt (25 extra (make)deps to pull) core/iputils depends on extra/docbook-xsl (27 extra (make)deps to pull) core/udev depends on extra/gperf (0 extra (make)deps to pull) core/udev depends on extra/libxslt (25 extra (make)deps to pull) core/e2fsprogs depends on extra/bc (0 extra (make)deps to pull) core/sqlite3 depends on extra/tcl (0 extra (make)deps to pull) core/ca-certificates depends on extra/ruby (25 extra (make)deps to pull) the actual deps are only displayed when there are less than 10. Signed-off-by: Xavier Chantry <shiningxc@gmail.com> Signed-off-by: Aaron Griffin <aaronmgriffin@gmail.com>
Diffstat (limited to 'cron-jobs/integrity-check')
0 files changed, 0 insertions, 0 deletions