Hey!
I've been watching this thread and have not found it very constructive so far. I
beleive the subject seserves more
interest...
As an ex-debian user, and current happy mdk user (for both, SERVER and Desktop) I have
to agree with a statement
made earlier in the thread:
Both package mgmt systems have their goods and bads, my experience confirms it. For
sure it looks like RPM has been
adopted as a standard. So why not improve RPM rather than fighting about which one is
better, which one screws up
the most, which one.....#$%^#&!$!%^&@
I think what's lacking the most with RPM is a console based system (kinda like
dselect) that uses apt like
principles - i.e.: you select a package to install or upgrade from an rpm repository
and all dependencies get
satisfied by downloading the required packages after confirmation from the user(Guys @
mdk, you already have the
algos ready from your 7.1 DrakX install script which by the way is really slick!).
Although I agree totally that
mdk is aimed at the desktop and therefore GUI based apps, I truly beleive that it
would be beneficial for mdk to
come up with such a tool. Think about upgrading a remote system from a telnet or ssh
session for example.
By the way, rpmdrake has never worked for me: it always hangs on generating
dependencies list - gendepslist2 (I
posted a help msg here about it but never got an answer:((()
Anyways, I just thought I'd put my $0.02 in, just to mention some lacks I see and
experience in RPM... Some of you
may think it's pointless, but I spoke anyways :)
Cheers everyone!
Peace,
Patrick.
