Matthewβs response caused a lot of emotion, because he still lacks small details. The general team will be:
# yum --nogpgcheck localinstall <package1_file_name> ... <packageN_file_name>
The above package_file_name may include a local absolute or relative path or be a URL (possibly even a URI).
Yum will look for dependencies among all the package files specified on the command line, and if it cannot find the dependencies, it will also use any configured and included yum repositories.
Neither the current working directory, nor the path to any of the package_file_name will be found, unless any of these directories has been previously configured as the included yum repository.
So in the case of OP, the yum command is:
# cd <path with pkg files>; yum --nogpgcheck localinstall ./proj1-1.0-1.x86_64.rpm ./libtest1-1.0-1.x86_64.rpm
will do, like rpm :
# cd <path with pkg files>; rpm -i proj1-1.0-1.x86_64.rpm libtest1-1.0-1.x86_64.rpm
The difference between these yum and rpm will only be visible if one of the packages listed has additional dependencies on packages NOT listed on the command line.
In this case, rpm will simply refuse to continue, while yum will use any configured and enabled yum repositories to look for dependencies and may possibly succeed.
The current working directory will NOT be found in any case, except when it was previously configured as the included yum repository.
Artur Opalinski Jan 30 '18 at 8:54 2018-01-30 08:54
source share