Any Equivalent to YaST1's ability to install arbitrary RPMs?
One of my favorite things about YaST1 was the way it could be pointed at a directory full of rpm files and it would tell you which were already installed and if the versions in the directory were the same or different from those already installed. I can't see how to use YaST2 to do the same thing, but perhaps there is another "rpm manager" tool or front-end that will allow me to do this. Any suggestions? -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Sunday 05 May 2002 02:48, Robert Paulsen wrote:
One of my favorite things about YaST1 was the way it could be pointed at a directory full of rpm files and it would tell you which were already installed and if the versions in the directory were the same or different from those already installed.
I can't see how to use YaST2 to do the same thing, but perhaps there is another "rpm manager" tool or front-end that will allow me to do this.
Any suggestions?
This is the ongoing complaint that so many of us are having. There has been talk of people reinstalling yast1 to accomplish this, check the last couple of days emails esp for ones from Joost. Please send an email to feedback@suse.de and let them know. Perhaps if enough of us complain we will get some action to include it in yast2 dids
dids wrote:
On Sunday 05 May 2002 02:48, Robert Paulsen wrote:
One of my favorite things about YaST1 was the way it could be pointed at a directory full of rpm files and it would tell you which were already installed and if the versions in the directory were the same or different from those already installed.
I can't see how to use YaST2 to do the same thing, but perhaps there is another "rpm manager" tool or front-end that will allow me to do this.
Any suggestions?
Supposing you have a large collection of RPM files in a directory, the simplest solution to update only the installaed packages is: open a terminal, change to the directory where RPMs are, and ... rpm -Fvh *.rpm see the man page of rpm for an explanation of the -F (freshen) option. If you run into dependencies problems use --nodeps option or try to resolve them yourself. Yast1 did not check dependencies, so we are in no worse shape. -- Rafael
participants (3)
-
dids -
Rafael E. Herrera -
Robert Paulsen