> 1 - The original point I was commenting on was that the 'drake' > installer was getting more complicated by being broke into several > sections. This is a fundamentally flaw concept for newbies to take > on. We can disagree on this, but having more than one program to take > care of installing and removing software might just be more involved.
so, i guess you propose to have only one rpmdrake program ? Now, , for the same reason, should we unite all wizard related to Network in one super wizard ? No, i don't think. This would be confusing. But the same applies, why should people have one program to share the connection, and one to edit the firewall rules ? Don't forget that rpmdrake should not be run from the command line, but from the MCC or from kde-gnome-whatever menu. So, of course, they are two separate program, but, since they are designed to be launched as module in the mcc, this make sense. I agree, maybe mandrake lacks a powerful package management graphical tool, but, since ressources are scarce, they needed to choose between newbie and more advanced user, and clearly, they favored the newbie. -- Micha�l Scherer
