On Sat, Jan 26, 2008, Jeff Johnson wrote:

> Perhaps
> 	Requires: verify(N) = E:V-R
> will simplify some of your OpenPKG framework hardening.
>
> Easy way to exercise the verify(...) probe is
>     mkdir -p /etc/rpm/sysinfo
>     echo "verify(zlib)" >> /etc/rpm/sysinfo/Requirename
>
> Return code is goofy atm, the I/O spew while checking dependencies
> will need some fiddling, and there are some obvious generalizations to
>     Requires: verify(*)		# same as -Va
>     Requires: verify(/path)	# same as -Vf path
> and a few extensions that I can think of, I'm sure you can think of some
> uses too.

Interesting. But what happens on "verify(foo)" if a %config file of
package "foo" is modified. It is already causing "verify(foo)" to fail?
In on short: when in particular does "verify(foo)" fail and when does it
succeed?
                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com