-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
seth vidal wrote:
On Tue, 2007-08-21 at 16:36 +0200, Jeroen van Meeuwen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
seth vidal wrote:
On Tue, 2007-08-21 at 14:12 +0200, Jeroen van Meeuwen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This [1] is a rather ugly dependency checker for any number of repositories. It uses yum to search for requirements that cannot be resolved.
I thought maybe because there's no dependency checking yet on updates and such (don't know the details), and I needed this anyway, I'd just dump it here and collect some useful comments.
How does this differ from repoclosure in yum-utils?
I'm assuming that if I use repoclosure with the system's yum configuration, it tells me what it can't resolve just like when I would yum install the package with missing dependencies -so correct me if I'm wrong to assume that:
A random example from repoclosure:
# repoclosure -c /etc/yum.conf -a i386 -n [...snip...] package: dkms - 2.0.16-1.fc7.noarch from fedora unresolved deps: kernel-devel [...snip...]
# yum install dkms [...snip...] Installing: dkms noarch 2.0.16-1.fc7 fedora 84 k Installing for dependencies: kernel-devel i686 2.6.22.1-41.fc7 updates 4.7 M [...snip...]
I'm not sure where it differs, but apparently repoclosure does some things different from yum, as I'm sure this ugly depchecker does too.
repoclosure doesn't care about your local rpmdb. It takes a look at all the repositories you have and makes sure you have depset closure across all of them.
-sv
Right that I figured, but what I don't understand is it reports dkms has missing requirement 'kernel-devel'.
- -- Kind regards,
Jeroen van Meeuwen - -kanarip
- -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08