Here is what I would conclude from this thread so far, having read all of the concerns raised about RPM: (See comments below)

Peace,

Patrick

Bryan Paxton wrote:

On Tue, 20 Jun 2000, Guy T. Rice wrote:
> I think the answer is to simply build tools on top of RPM.  After all, that's
> what Debian did, except they did it on top of pkg_add (or whatever it was,
> I don't recall -- pkg_add rings a bell but I think that's because I also
> admin two BSD boxes).  In any case, just as Debian built some really nice
> tools on top of their basic package installation tools, Mandrake could build
> some very nice tools on top of RPM to do everything Debian's package mgmt
> system does, without sacrificing RPM & RedHat compatibility.


Now ... I think we all agree on this and I'm glad to see I'm not the only one wishing for a dselect type of frontent for RPM.  And we're right, rpmdrake is good only when it works and when we have a GUI.  CLI frontent to RPM is a MUST HAVE for Mandrake.

*nod* I now agree this is the way to go, of course how does one set up the
repos, dep lists, etc......... for rpm ?


Of course it raises lots of questions, but where do we go from there...  Build on top of the rpmfind tool???

MANDRAKE PEOPLE, I beleive everyone who has participated in this thread is willing to contribute...  Guidelines are necessary here and maybe you should contribute to LBS in that matter!?!

 
To wrap up, I'd say that we should not remain proprietary but rather help Mandrake pioneer a high performance, reliable  canditate piece of software for setting a standard in rpm frontent a la dselect (CLI or GUI).  Why non-proprietary??? Just because (and I quote Amien Salie here in a previuos message he posted in this thread) " Why did Unix fail where Microsoft succeeded?" And the simple answer to this is .... "the Unix vendors were devided against themselves".
 
 


Peace,

Patrick

Reply via email to