Description of problem: It is hard to work out how to minimise the load (now that the minimal system checkbox has been withdrawn) when rpm -q --whatrequires TARGET has a rather inconsistent interface How reproducible: rpm -q --whatrequires csh rpm -q --whatrequires /bin/csh rpm -q --whatrequires /usr/lib/beecrypt.so.6.4 rpm -q --whatrequires beecrypt.so rpm -q --whatrequires beecrypt.so.6 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Dependencies to be shown for most forms of the TARGET Additional info:
On behalf of everyone, I'd just like to say...Huh?! Your report makes no sense, largely because you ignored almost all those blanks you were supposed to fill out. The end result is that you make no sense. Try making some please. Thanks.
Well actually I gave you a sequence of 5 whatrequires queries under how reproducible - Perhaps how reproducible should read: every time, rather than listing the method... Ok here we go Steps to reproduce rpm -q --whatrequires csh rpm -q --whatrequires /bin/csh rpm -q --whatrequires /usr/lib/libbeecrypt.so.6.4 rpm -q --whatrequires libbeecrypt.so rpm -q --whatrequires libbeecrypt.so.6 Actual Results: + rpm -q --whatrequires csh no package requires csh + rpm -q --whatrequires /bin/csh mtools-3.9.10-2.fc6 + rpm -q --whatrequires /usr/lib/bbeecrypt.so.6.4 no package requires /usr/lib/bbeecrypt.so.6.4 + rpm -q --whatrequires libbeecrypt.so no package requires libbeecrypt.so + rpm -q --whatrequires libbeecrypt.so.6 beecrypt-4.1.2-10.1.1 rpm-4.4.2-32 rpm-libs-4.4.2-32 rpm-python-4.4.2-32 Expected results + rpm -q --whatrequires csh mtools-3.9.10-2.fc6 + rpm -q --whatrequires /bin/csh mtools-3.9.10-2.fc6 + rpm -q --whatrequires /usr/lib/bbeecrypt.so.6.4 beecrypt-4.1.2-10.1.1 rpm-4.4.2-32 rpm-libs-4.4.2-32 rpm-python-4.4.2-3 + rpm -q --whatrequires libbeecrypt.so beecrypt-4.1.2-10.1.1 rpm-4.4.2-32 rpm-libs-4.4.2-32 rpm-python-4.4.2-3 + rpm -q --whatrequires libbeecrypt.so.6 beecrypt-4.1.2-10.1.1 rpm-4.4.2-32 rpm-libs-4.4.2-32 rpm-python-4.4.2-32 Additional info The TARGET of the --whatrequires query is something of a movable feast --- is the path required or not? are the version numbers complete omitted or partial, why not report the dependency against the package (stem / fully qualified) as well as the individual files? I trust that is clearer
Whatrequires has always been a literal match on the requires not all provides of the packaege. Also creating a paired down install is easily done by using kickstart - try using an empty %packages (for just Core and Base) or for even less use: %packages --nobase Please note this option, it is very easy to end up with a system that does not fully boot to a login prompt as you will need to list all the packages required to get that much functionality. There is no package called csh, rpm -qf $(which csh) tells you the package name. You can easily script a solution: rpm --qf '[%{providename}\n][%{filenames}\n]' -q $(rpm -qf /bin/csh) | xargs -i rpm --whatrequires -q {} Or easier still - yum install yum-utils and you can use repoquery to see what the relationships within the distro are (you may wish to limit it by repoid to core). repoquery --whatrequires --alldeps tcsh