On Nov 19, 2007 12:42 PM, Scott Horowitz
Suppose you have a package which depends on provision>=2.0-2 * 'provision 2.0' -> OK
If a devel adds 'provision>=2.0-2' as depend, then this implicitly means that not "all" 'provision 2.0-x' version would satisfy this depend; and 'provision 2.0' says no info about -x...
I agree with Nagy; I think just about everyone would find 2.0 meeting a >=2.0-2 provision to be illogical.
I'm pretty sure normal deps already act this way. That is, the vercmp function will check the pkgrel only if it exists. If it doesn't exist, it doesn't care. This gives us flexibility. For instance, lets say we have 19 packages that depend on foobar 1.7. If we add "foobar=1.7-1" to every package, that's fine. Later, if we change, say the url=() in the PKGBUILD, we now need to rebuild all of the packages that depend on foobar with explicit versions. It's just messy. Instead of forcing it one way or the other, leaving it open like the current vercmp does gives the power of this decision to the packager.