mirror of
https://github.com/ostreedev/ostree.git
synced 2024-10-26 08:55:19 +03:00
41 lines
1.6 KiB
Plaintext
41 lines
1.6 KiB
Plaintext
* Documentation
|
|
|
|
* Rethink commit objects
|
|
- Drop the a{sv} per https://bugzilla.gnome.org/show_bug.cgi?id=673012
|
|
- Do we need freeform subject/body? Or should it just be a generic
|
|
key-value store?
|
|
- Optional non-object metadata; e.g., "detached" GPG signatures which
|
|
are in the same file (to avoid double HTTP requests)
|
|
|
|
* Hybrid SSL pull (fetch refs over SSL, content via plain HTTP)
|
|
|
|
* ostree-commit: multithreaded/async (basically compute sha256 in parallel)
|
|
- Also speed up devino cache by having a big mmappable file that maps from
|
|
(device, inode) -> checksum. We need to keep the cache up to to date;
|
|
investigate something like http://www.sqlite.org/wal.html for having
|
|
a shared file.
|
|
|
|
* GPG signatures on commits, and more generally, extensible metadata
|
|
associatible with commits. So for example, commit objects could
|
|
also contain secondary checksums of the *entire* content, which
|
|
would allow for stronger verification.
|
|
|
|
* Indexed metadata pack objects for bare repositories at least;
|
|
no reason to inflict thousands of little metadata files on
|
|
each client.
|
|
|
|
* Efficient delta format between commit objects, somewhat like
|
|
Chromium autoupdate: set of operations to perform given previous
|
|
object set to create new objects.
|
|
|
|
* Tests of corrupted repositories, more error conditions
|
|
|
|
* ostree admin install: Pull in host data, such as uids and /etc/fstab
|
|
|
|
* ostree admin undeploy <osname> <tree>
|
|
|
|
* ostree admin uninstall <osname>
|
|
|
|
* Possibly move all of the "regular" commands to be "ostree repo" ? Then
|
|
we'd have: "ostree repo pull", "ostree repo ls", etc.
|