![]() ![]() One needs to remove it for a real installation. In case you are provided of an RPM file, you can use the same yum install command, which is equivalent to the obsolete yum localinstall command, as follows. Whereas following would succeed: $ rpm -Uvh -test some-2.0.0.rpm Now, there are special cases, e.g., kernel where it will be installed on the system side-by-side with the old one, unless you manual invoked a rpm -Uvh kernel*.rpm command.Įquivalent command to the yum localinstall would be two-fold, # This will fail if some-2.0.0 is designed to obsolete some-1.0.0 Here is the difference of 'yum install' and 'yum localinstall', which are quite simple.yum install packagename - basically searches the package in the repositories, download them along with dependencies and installes it. yum resolves these dependencies whereas a rpm -ivh won't do it. This tells that yum is going to update the package and remove the old one. Use the following command to install the stage libraries downloaded to the current directory: yum localinstall --1.noarch.rpm -<.> Package foo.x86_64 0:2.0.0 will be an update > Package foo.x86_64 0:1.0.0 will be updated The yum command is the primary tool for getting, installing, deleting, querying, and otherwise managing Red Hat Enterprise Linux RPM software packages from official Red Hat software repositories, as well as other third-party repositories. Looking at your some-package, if you would run yum localinstall some-package-2.0.0.rpm (note, not with -y), then you would see message from yum, something like this: Resolving Dependencies rpms packaged with foo-version-release.rpm gets obsoleted by the same package foo with version++ and/or release++. yum deplist nfs-utils provides yum provides bin/top README.top yum provides /README. Answer is, it depends on how some-package is packaged.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |