Colin Walters 24faf942df compose: Add --add-metadata-from-json ... I'd like to embed structured metadata about the originating git repository. See [this example](https://pagure.io/fedora-atomic-host-continuous/c/142b12020d7efe18b56d039304efea102a210790?branch=master). However, I think what we really want here is a *single* value which has subkeys. One thing in the back of my mind too is...we could use this to enhance our "change detection". Right now we checksum the sack, treefile, and treecompose-post. But down the line, I'd like to support more sophisticated postprocessing, where the script might reference external files or the like. In that case, we could stop checksumming the post script, and rely on whether or not the git repo changed. (This would conversely mean we would do a build even if e.g. the repo's `README.md` changed, but we can address that with a post-assemble content check). Anyways though, for now, this gets us the ability to more easily drop more structured metadata in the commit, whether it's input git repos, tests that passed, etc. Note a trap that bit me here: since the metadata we write here is *host* endian, but `ostree show --raw` byteswaps (it needs to since the core ostree variant is always big endian), we get inverted numbers if the host is little. I think we should probably canonicalize our metadata to big endian; this should be pretty backwards compatible since I doubt anyone has been adding raw numbers so far. Closes: #676 Approved by: jlebon		2017-03-14 18:17:07 +00:00
..
app	compose: Add --add-metadata-from-json	2017-03-14 18:17:07 +00:00
daemon	rebase: Update man page for syntax, print if just changing remote	2017-03-13 14:45:30 +00:00
lib	tree-wide: Use autoptr cleanup for HyQuery	2017-02-24 18:55:36 +00:00
libpriv	core: Don't try to chmod() symlinks	2017-03-13 17:53:51 +00:00