Working out some remaining issues in perl-URPM for dealing with upgrades from stable releases I became aware of some different behaviour for suggests giving headaches..
First of all, ie. 'rpm -q --requires foo' will return both "regular" requires and suggests, is this really correct behaviour? For rpm 4.6 it will also treat the suggests as "regular" requires as well, ie. trying to install packages built with rpm 5.3 without satisfying suggests will return in dependency error. I'm not sure about what's considered as "correct" behaviour or not, working around it in perl-URPM can be done.. IMHO 'rpm -q --requires' shouldn't return soft dependencies, and older rpm versions shouldn't treat these as such either, ignorance of not knowing better being fairly obvious.. ;) -- Regards, Per Øyvind ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
