Hello.

I am seeing a lot of problems with cooker RPM's.  For example, my latest 
install quanta3.1-1mdk.i586.rpm

On attempted install, this aborts with messages showing several failed 
dependencies.

Yet when I use regular mandrake releases, I never see dependency problems.  It 
would seem the files required are already installed, with the package or 
retrieved and installed transparently.

Why is this such a problem with cooker releases ?

In the BSD's using the package system, it is setup to check for the required 
filkes and libraries plus version, if it doesn't find it, it checks the cdrom 
and then goes to the net, downloads and installs it, and continues with the 
install.  The BSD's have done this for several years.

I thought this dependency/stop install problem had been fixed in the RPM 
system with added capability (go get the required dependency RPM) at least 
Three years ago.

Do we still have to manually go and install, each and every dependency listed 
in this day and age.

Opinions ?  Bricks, clubbings...well you know.

Please enlighten me.

Regards...Martin


Reply via email to