On Fri, Apr 02, 2004 at 04:11:05PM +0200, BlueHat wrote: > Am Fre, den 02.04.2004 schrieb Dave Cross um 13:48: > > On Fri, Apr 02, 2004 at 01:19:49PM +0200, BlueHat wrote: > > > > > > I've done this (as 'root'), but it does'nt work. By the next try to > > > install wdg it's the same, rpm requires those modules. > > > > Then you can either force the rpm installation (it should work as the > > modules _have_ been installed, or you can track down and install rpm > > versions of the modules. > Thanks, this works! Could you explain why? Not sure what you mean by "this" as I don't know which of the two options that I suggested you used. But here's an explaination of what has happened. You wanted to install an rpm of some software and that rpm has some dependencies which are given in terms of rpms. Now the actual software doesn't care whether the Perl modules it needs are installed as rpms or directly from CPAN. It just needs the modules to be installed. So if you install the modules from CPAN, the rpm database isn't updated and if you try to install the original rpm bundle, then it will still complain as rpm doesn't think that the modules are installed. However, you know that the modules _have_ been installed so you can safely force rpm to ignore the dependencies. But if you find rpm versions of the Perl modules and install those instead, then the installation will be registered in the rpm database and you won't get any warnings when installing your software. Does that help? Dave... -- New .sigs Running in please parse
