Quoting Kin C Wong <[EMAIL PROTECTED]>: > I am hoping that one day it won't matter to me what distro it is, I can > still do what is required. Some of the training material that I have come > across on the web that is Red Hat based does not use rpm for installation > and I have come across the comment more than once that rpm do not resolve > dependencies as well for installations. (ok, I am starting to feel > uncomfortable -- someone straighten me out if this is bogus). One of the > reasons why we did not move to Suse was, we know how to start and stop > processes in Red Hat, knew where the configuration files were and knew how > to set the tcp ip information. I loaded up a copy of Suse Server edition > that we got from Novell and was presently impressed. All the settings that > need to get to was easily accessible (I think Clug still has a couple of > copies left if you are interested). This is what is known as dependency hell. This is when you are trying to install a piece of software, and you have to hunt around for all sorts of dependencies to get it installed. It is true that Red Hat uses rpm as their package manager system. On its own, rpm does not resolve dependencies for you. Historically, this was easier of debian based systems because apt would resolve dependencies and download the needed packages. However nowadays just about every system comes with some sort of system to do this for you. On rpm based systems you can use yum or apt4rpm. Mandriva also comes with a tool called urpmi to do this. On Slackware there are a number of pieces of software including slapt-get. However, you cannot totally get away from dependencies when you are trying to install third party software, or compiling from source. One of th
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
