> Yeah, inconsistent dependencies are why I shied away from rpm.
> They made life harder than not having dependency checking at all.
> My current philosophy is to eschew automated dependency
> checking (which the minimalist Slackware tarball approach does
> not support last time I checked) and learn the dependencies
> yourself. That way you are in control no matter what distro you
> are working under. As long as you are able to _cleanly_ install
> and uninstall packages with a single command, managing dependencies
> is not as big of a headache (in theory).

This kind of mindset is not sustainable if you have more than one box to
maintain.  Knowing every nook-and-cranny of each server one deploys is
simply impractical.

What is important is that one is capable of analysing the setup of a
system with the output of (a) query command(s), and apply certain
best-practice principles with the least possible effort and thought.
This is the reason the features of RPM are what it is.





_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
[EMAIL PROTECTED]

Reply via email to