First shot at rpm-ostree command reference #89
Conversation
| OS distribution. This means it is possible to switch your Fedora 26 Atomic Host | ||
| to a version of CentOS Atomic Host. While this is not likely to be done on a | ||
| production system, it can be useful in certain testing scenrios. | ||
|
|
There was a problem hiding this comment.
We should add a relative link here to the package layering doc. Maybe something like:
See the link:../using_ostree/ostree_mutations/package_layering.adoc[package layering section] for more information on package layering.
?
|
Minor nit, otherwise LGTM! 👍 |
| The `rebase` command also allows you to switch your system to an entirely new | ||
| OS distribution. This means it is possible to switch your Fedora 26 Atomic Host | ||
| to a version of CentOS Atomic Host. While this is not likely to be done on a | ||
| production system, it can be useful in certain testing scenrios. |
miabbott
changed the title
|
There are some additional commands that need to be fleshed out, so I labeled this as WIP |
miabbott
changed the title
|
I managed to fill out something for all the Removing WIP designation. |
| === `rpm-ostree compose tree` | ||
|
|
||
|
|
||
| == Experimental interface |
There was a problem hiding this comment.
Let's drop this section; the ex livefs and ex override are going to be covered elsewhere. The other two are really experimental.
| === `rpm-ostree db version` | ||
|
|
||
|
|
||
| == Composing an ostree commit |
There was a problem hiding this comment.
This one is also going to live elsewhere, right?
| @@ -0,0 +1,251 @@ | |||
| [[rpm-ostree-command-ref]] | |||
| = {product-title} rpm-ostree Command Reference | |||
There was a problem hiding this comment.
This all seems fine to me...I am just uncertain about the big picture here versus the docs that live in rpm-ostree upstream.
Offhand...it feels like upstream should be more detailed, but this doc covers a high level? And we link to upstream?
There was a problem hiding this comment.
@jlebon and I were discussing ideas on how to have these docs co-exist, especially stuff like this that is in the category of 'command reference'. Mirroring the upstream docs here might be a solution.
I'm happy to keep this high-level and make changes to adjust; the original content was from upstream, so I was just massaging it a bit. If you think any changes here should be moved to the rpm-ostree repo (or readthedocs), just let me know.
@jberkus Any thoughts on the subject of command reference docs (like this) and where they should live?
There was a problem hiding this comment.
I opened an issue to talk about this here: #95.
No description provided.