On Mon, Jul 07, 2008 at 07:10:59PM -0400, Jeff Johnson wrote: [...] > E.g. here are the immediate precursors of the bash package: > > $ rpm --needswhat bash > bash-3.2-22.fc9.i386 > coreutils-6.10-25.fc9.i386 > glibc-2.8-3.i686 > ncurses-5.6-16.20080301.fc9.i386 > ncurses-libs-5.6-16.20080301.fc9.i386 > > IOW, those packages need to be installed to satisfy bash dependencies. [...] > E.g. Should --needswhat/--whatneeds display all, rather than just > adjacent, package nodes? > > Adding the necessary looping isn't very hard, but I need some luser > input first.
From one side, recursive --needswhat looks useful for such tasks as requirements closure. From another side, it is not obvious how recursive --needswhat should traverse virtual packages where more than one alternative is available. -- ldv
pgpLBCgB4C9fW.pgp
Description: PGP signature
