what mandrake needs
 

i'm starting this topic because i think that mandrake lacks something i'm gonna send my suggestions (and yours if you have any) .
my suggestions:

- must have more control over installation. If i doulble click an .rpm the installer opens then automaticly closes only saying {to satisfy dependencys the following pakage has being installed: **************}. Mabe Alittle info whould help like: the pakage description, the dependancys and what it provides and where to. I know you can do this is knosol but typing 'rpm --provides --requires ************8' isn't that conveniant.

-also tarballs should have a right clicked menu option to install with things like install by default (./configure , make , make install) also should probe the shell script for options like make install, make dependant, make uninstall, make user, make test. and with the same thing as above. This also helps you create shortcuts

-Someone should really write a script (not me i only can write microsoft) for introductory to mandrake like when you click the /dev folder a little help thing pops up and says all the port and system thingos are here.

-cups should adopt plugins like the pss port script file. Where you have the printer and you just insert a file into /user/lib or something (i don't really get the system now)

- update dosn't detect if you actually have the program installed. I can install updates to things i don't have... duh

- this is for open source develops in general. Why create :
-rpm##.##.##.*****##.##.9-mdk.rmp
-rpm##.##.##.*****##.##.9.2-mdk.rmp
-rpm##.##.##.*****##.##.10-mdk.rmp
-rpm##.##.##.*****##.##.4-gnt.rmp
ect
when you can create a source rmp
-rpm##.##.##.*****##.##.scr.rmp

my suggestion to you is to do more reading. You can do all these things if not get around them.