On Tuesday 25 June 2002 22.33, Jon Clausen wrote:
Maybe separation is a nonissue. Maybe it's to do with apps depending on dev/base, and dev depending on base, and it makes sense installing in that sequence? *Even* if you --force...
If there's a requirement on the sequence of packages (there isn't, except for dependencies) then rpm would handle it if you install all of them in the same command.
If you *have* downloaded the lot, it could be kind of laborious to verify which rpms were already installed. So how about using -F instead?
Sure, why not. There's no difference in the method of installation between -U and -F except, as you say, that -F will only grab the packages already installed on the system, so -F would work as well.
and let rpm sort out the dependencies.
Which was already tried, and reported to fail. Am I mistaken in that dependencies *will* fail in this situation, because of catch 22?
Nope, it wasn't tried as far as I can tell. As I read the messages on this topic, all that was tried was to rpm -Uvh each package separately. The only way this can fail if the other method succeeds (as far as I can see, perhaps I should add) is if there are too many packages, so they won't all fit in the parameter array.
Certainly. When I upped KDE, it didn't much matter to me anyway, because I hadn't fully moved from 7.3 - it did, however work quite nicely. Also, I could have missed it, but I don't recall any problems reported as a result of this way to upgrade kde...(?)
yet
Especially --force could end up overwriting files you don't want to be overwritten. Don't rely on the package maintainer being infallible. If there's an error, it's probably a good idea to try to find out what the error means.
Always. Though from what I understand from the messages about this topic, the errors basically amount to catch 22. But sure, stuff can go wrong. Hence my "words of warning"... back up your .files, check ownerships/permissions afterwards. Certainly something *did* sort of, kind of go wrong for me. But if the worst that happens (my experience) is that some files end up being owned by root, it's not really that bad...
If you have a new package (I know this happens with ximian packages) that "owns" a file previously owned by another package it won't install if you just rpm -Uvh it. It will install if you --force it, but the file will be overwritten. That may be what you want, but then again it may not. Caveat installer. //Anders -- `When I use a word,' Humpty Dumpty said in rather a scornful tone, `it means just what I choose it to mean -- neither more nor less.'