I don't usually, but... 10049
snips
snips So it's an RPM file. An incorrectly formatted one. Eventually, you'll figure that out. The computer figured it out ages ago; when are you going to catch up? You need to...
No, they don't, since neither KDE nor Gnome have any concept of RPMs. Once again, demonstrating a fundamental cluelessness about, well, pretty much everything.
What they do, in fact, is hand off appropriately-extensioned files to handler applications; jpg to the image viewer, html to the browser, rpm to the package manager and so forth.
Kelsey Bjarnason Spare me your pedantics. They don't reduce the sheer stupidity of Linux-KDE-.rpm installer reporting an empty text file...
Of course, the helper application must then proceed to actually validate the file. In the case of an html document, this means ensuring it can be read and displayed. In the case of an rpm, it means parsing its contents and attempting (if the contents are valid) to install it.
Hmm, I wonder what sort of message an *installer* application is going to display during the *installation* process. Something like "Installing package", perhaps? Makes sense. Hmm, validating the package is part of the installation process... so it's no surprise to see that message during that phase, now is it? Guess not.
You do, of course, have documentation that "KDE" actually tried to install said broken package, right? We're quite sure it launched the package manager; we're quite sure the PM started the package validation process. Do you have any support for the notion that it subsequently carried on and actually tried to perform the installation phase? Or did it simply barf out and issue an "Install process completed" or some such, which is, after all, exactly what happened?
Linux Advocacy from Newsgroups