I have seen several discussions about proper behavior of installroot and often it happened that what was requested by one user several others declined. But all of them had one thing common, that they would like to have proper description of installroot behavior. Now I can proudly announce that installroot entered new era where the behavior is slightly changed, but documented in detail.
Basically what was changed
- config file and reposdir are searched inside the installroot first. If they are not present, they are taken from host system. But when a path is specified within command line argument (–config= in case of config file or –setopt=reposdir= for reposdir) then this path is always related to the host with no exceptions.
- pluginconfpath is taken from installroot
If you think that reposdir behavior is not so new, you are completely right, because it is same like in YUM.
The documentation was also enhanced with following examples:
dnf --installroot=<installroot> --releasever=<release> install system-release
- Sets permanently the
releaseverof the system within
<installroot>directory from given
dnf --installroot=<installroot> --setopt=reposdir=<path> --config /path/dnf.conf upgrade
- Upgrade packages inside of installroot from repository described by
--setoptusing configuration from
I am really happy that I can say that additional information can be found in DNF documentation. Please have a fun with DNF.