packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

lib/repo: Clean up OstreeRepo docs 

This fixes typos and grammar in the docs for OstreeRepo, and copies the
information about OSTREE_REPO_MODE_BARE_USER_ONLY from ostree-core.h

Closes: #1725
Approved by: jlebon
This commit is contained in:
Matthew Leeds 2018-09-18 13:36:06 -07:00 committed by Atomic Bot
parent 3c46bcdb50
commit 6b37fe8310
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
src/libostree/ostree-repo.c
View File

@ -90,17 +90,19 @@ G_STATIC_ASSERT(sizeof(OstreeRepoPruneOptions) ==
* The #OstreeRepo is like git, a content-addressed object store. * The #OstreeRepo is like git, a content-addressed object store.
* Unlike git, it records uid, gid, and extended attributes. * Unlike git, it records uid, gid, and extended attributes.
* *
* There are three possible "modes" for an #OstreeRepo; * There are four possible "modes" for an #OstreeRepo; %OSTREE_REPO_MODE_BARE
* %OSTREE_REPO_MODE_BARE is very simple - content files are * is very simple - content files are represented exactly as they are, and
* represented exactly as they are, and checkouts are just hardlinks. * checkouts are just hardlinks. %OSTREE_REPO_MODE_BARE_USER is similar, except
* %OSTREE_REPO_MODE_BARE_USER is similar, except the uid/gids are not * the uid/gids are not set on the files, and checkouts as hardlinks work only
* set on the files, and checkouts as hardlinks hardlinks work only for user checkouts. * for user checkouts. %OSTREE_REPO_MODE_BARE_USER_ONLY is the same as
* A %OSTREE_REPO_MODE_ARCHIVE_Z2 repository in contrast stores * BARE_USER, but all metadata is not stored, so it can only be used for user
* content files zlib-compressed. It is suitable for non-root-owned * checkouts. This mode does not require xattrs. A %OSTREE_REPO_MODE_ARCHIVE
* (also known as %OSTREE_REPO_MODE_ARCHIVE_Z2) repository in contrast stores
* content files zlib-compressed. It is suitable for non-root-owned
* repositories that can be served via a static HTTP server. * repositories that can be served via a static HTTP server.
* *
* Creating an #OstreeRepo does not invoke any file I/O, and thus needs * Creating an #OstreeRepo does not invoke any file I/O, and thus needs
* to be initialized, either from an existing contents or with a new * to be initialized, either from existing contents or as a new
* repository. If you have an existing repo, use ostree_repo_open() * repository. If you have an existing repo, use ostree_repo_open()
* to load it from disk and check its validity. To initialize a new * to load it from disk and check its validity. To initialize a new
* repository in the given filepath, use ostree_repo_create() instead. * repository in the given filepath, use ostree_repo_create() instead.