![]() rpm packages stored in the given remote repository. repo file to locate the actual manifest file that describes the. ![]() repo file under examination.ĭnf install has the intelligence to parse and analyze the information in the. repo files in the directory /etc/ to get the URL of the repository associated with the. If the package reference can't be found in the local cache, dnf install looks in the. This file might exist locally in the dnf (or yum) cache of the local machine, which is where dnf will look first to find a reference to the package location. Understanding RPM package discovery and installationĭnf (or yum) finds a package to install by doing a lookup on what is called a repository manifest file. But, before delving in, let's review how RPM discovers a package on the internet and then installs it. repo file when managing RPM packages on a given machine. repo file but also describes the logic that's applied to a. This article describes not only the format specification for a. ![]() This article goes to the next level of detail to describe the format specified for a. repo files stored in the /etc/ directory of the local machine play a critical role in discovering, installing, and managing RPM packages. rpm package on a local computer running the Red Hat Enterprise Linux, Fedora, or CentOS Stream operating system. The previous article in this series, How does RPM package discovery work?, described how the RPM package management technology discovers and installs an.
0 Comments
Leave a Reply. |