On Thu, 2004-12-30 at 10:41 -0500, John Van Ostrand wrote: > That is a problem between keyboard and chair but not at my desk. It's > the package maintainer.
Not in this case I suspect. >From your previous email: > I tend to bend the rules from time-to-time, installing > something from a tarball instead of an RPM so I use rpm's --nodep > after which apt-get seems to refuse to work. The answer would appear to be staring you in the face, but you just don't seem to see it. > And yes, my main complaint about apt-get is that it can not keep up with > oddities. I could not find an option to override certain checks, or to > allow for event the smallest inconsistency. Rpm has it (--nodeps, -- > force, etc) then shouldn't the tool that sits above rpm support > something similar? If you aren't able to fix the mess you create when you use --nodeps or --force, then don't go there. Those options aren't there for people like you who get annoyed when the package manager tries to stop them doing something stupid. In fact, probably it would be better if they weren't there at all. I suggest you learn to trust RPM. It is far more likely to be right than you are, as you have already demonstrated. Do yourself a favour and forget you ever heard of --force and --nodeps. FWIW, I have used Axel's RPMs for myth 0.15, 0.16, and currently the CVS RPMs. On FC2, now FC3. I've never had a single dependency problem. But then I've never used --nodeps either. Cheers, Martin.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
