Steve Fox wrote:
In the real world, sysadmins just find a solution (like redoing the crap ass RPM someone made) and move on with life. If you don't like dependancy checking, then don't use urpmi. Use the plain rpm command. Write your own scripts as a wrapper. Or just patch urpmi yourself for your own needs. It's not rocket-science! ;)On Mon, 2003-01-06 at 23:19, Vox wrote:I actually like to think that urpmi getting old unresolved deps flagged is A Good Thing(tm). If you don't care for deps, don't use a package *manager*.
I totally appreciate that for packages which are being
upgraded/installed. But for stuff that's not being modified, it
shouldn't worry about it.
The whole "all dependencies must always be resolved" is nice if you live
in your closed little world where smart packagers like Mandrake create
proper dependencies.
But in the Real World (tm), there are idiots who package things to fit
in their little world. They won't listen to me when I say to use a
"Requires: java" instead of "Requires: IBM-JDK".
Just don't advocate breaking a tool other people like for your *small* need of getting one damn broken rpm to smoothly work! Find a better tool for your needs or create your own tools from scratch.
--
Bryan Whitehead
SysAdmin - JPL - Interferometry Systems and Technology
Phone: 818 354 2903
[EMAIL PROTECTED]
