Ralph Shumaker wrote: [Snip - needs to get a single file from an rpm]
OK, rpm2cpio (thanks, didn't know about it) is lots more elegant than rpm --root targetdir --relocate=targetdir --nodeps -ivh your.rpm and then fishing out the file from the new root. > To any and all, to whom it may concern: > What percentage of failed dependencies do you resort to "--nodeps"? If > you have an rpm that you want to install but it fails for a dependency, > do you jump to "--nodeps"? Are you reluctant to go there? Are you even > cautious about it? I'd be very cautious it actually installing it on a system. In this case it's just to extract the file(s). I'm not sure what the real end objective is here, though. If you fetch out a single executable file, either with rpm2cpio or by extracting to a new root with --nodeps (no package dependencies), it's not certain it will run on your system, because of library dependencies. What do you need which one file to DO ? David Looney -- This is not a novel to be tossed aside lightly. It should be thrown with great force. - Dorothy Parker -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
