Smarter dependency resolution

Let's say I want to install valadoc package which requires:

$ rpm -qp --requires valadoc-0.38.2-1.x86_64.rpm
/sbin/ldconfig
/sbin/ldconfig
libc.so.6()(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libc.so.6(GLIBC_2.4)(64bit)
libc.so.6(GLIBC_2.7)(64bit)
libcgraph.so.6()(64bit)
libglib-2.0.so.0()(64bit)
libgmodule-2.0.so.0()(64bit)
libgobject-2.0.so.0()(64bit)
libgvc.so.6()(64bit)
libpthread.so.0()(64bit)
libvala-0.38.so.0()(64bit)
rtld(GNU_HASH)
vala = 2:0.38.2-1

and in the packages repository there are two versions of vala package that satisfy libvala-0.38.so.0()(64bit) dependency - vala-0.38.1-1.x86_64 and vala-0.38.2-1.x86_64. What we get now?

$ poldek -i valadoc
[...]
Processing dependencies...
valadoc-0.36.0-1.x86_64 obsoleted by valadoc-0.38.2-1.x86_64
valadoc-0.38.2-1.x86_64: required "libvala-0.38.so.0()(64bit)" is provided by the following packages:
a) vala-0.38.2-1.x86_64
b) vala-0.38.1-1.x86_64
Which one do you want to install ('Q' to abort)? [vala-0.38.2-1.x86_64]

poldek asks which one we want to install even though vala-0.38.2-1 package is required directly by dependency vala = 2:0.38.2-1. Poldek should be smart enough to select it automatically and not ask questions.