On Sun, Nov 5, 2023 at 3:54 PM Samuel Sieb samuel@sieb.net wrote:
On 11/2/23 06:36, Christopher wrote:
On Wed, Nov 1, 2023 at 1:50 PM Kevin Fenzi kevin@scrye.com wrote:
On Wed, Nov 01, 2023 at 11:05:33AM -0400, Christopher wrote:
It's also not clear when this option would take effect. Would it take effect if I did `dnf install /path/to/local/file` or just when I did
no, because that looks up that file in your repos and downloads the repo version of the package.
That's not what I've seen. I've used this to explicitly install the Google Chrome RPM before from a local path... before the Chrome repo was set up, and it did not re-download the RPM from any repo. `dnf install ./google-chrome-stable.rpm`. I remember this because it was surprising to me that I didn't need to specify 'localinstall', that regular 'install' just worked. Ever since, I've assumed that 'localinstall' was just an alias for 'install' and didn't behave any differently. Perhaps that assumption is wrong, but that appeared to be the behavior I observed at the time.
This was ambiguous and I think you were both considering different meanings.
You can dnf install a local rpm file, but you can also give dnf a path to an actual file (e.g. /usr/bin/bash) that can be installed and dnf will find and install the package that contains it.
# dnf install /usr/bin/bash Package bash-5.2.15-3.fc38.x86_64 is already installed.
I was definitely referring to /path/to/existing/local/package.rpm, but I now understand the other behavior for /path/to/missing/file/to/find/and/install.
Thank you for the clarification! That makes sense now.