keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: improve install/uninstall help

Browse Source 
This adds some additional help to the man page and the RTD page around
using local packages with the install/uninstall commands.

Closes: #1388
Approved by: cgwalters
This commit is contained in:
Micah Abbott 2018-06-05 09:51:01 -04:00 committed by Atomic Bot
parent 479406e6a5
commit de42ef701f
2 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/manual/administrator-handbook.md
View File

@ -65,8 +65,13 @@ to use packages where it suits.
```
Will download the target package, its dependencies, and create a new deployment
with those packages installed. To remove layered packages, use `rpm-ostree
uninstall`.
with those packages installed. It is also possible to specify a local package
which is not part of a repository.
To remove layered packages installed from a repository, use `rpm-ostree uninstall
<pkg>`. To remove layered packages installed from a local package, you must
specify the full NEVRA of the package. For example, `rpm-ostree uninstall
ltrace-0.7.91-16.fc22.x86_64`.
By default, every `rpm-ostree` operation is "offline" - it has no effect
on your running system, and will only take effect when you reboot. This "pending" state is

8
man/rpm-ostree.xml
View File

@ -221,7 +221,8 @@ Boston, MA 02111-1307, USA.
Takes one or more packages as arguments. The packages are
fetched from the enabled repositories in
<filename>/etc/yum.repos.d/</filename> and are overlayed on
top of a new deployment.
top of a new deployment. It is also possible to specify a
local package that resides on the host.
</para>
<para>
@ -264,6 +265,11 @@ Boston, MA 02111-1307, USA.
top of a new deployment.
</para>
<para>When trying to uninstall a package that was installed
from a local RPM (i.e. not from a repository), you must
specify the full NEVRA of the package.
</para>
<para>
<command>--reboot</command> or <command>-r</command> to
initiate a reboot after the deployment is prepared.