[atomic-devel] Tree compose questions

[Jon Stanley <jonstanley gmail com>]

I've been doing some (perhaps crazy) experimentation with rpm-ostree
and composing my own trees, since Atomic upgrades are extremely
attractive to us at $DAYJOB.

I've noticed a few things that I'd like to point out and open for
discussion, particularly around building rpm-ostree repos for
enterprise use. First, I can't seem to find any inventory (other than
that which I can get with 'rpm-ostree rpm list') of what went into a
given commit in the ostree repo. It would be nice if one of the pieces
produced from a tree compose was a text file with what RPM's are in
that image.

It would also be useful (read: required - some software is very poorly
behaved wrt expecting a writable /usr) to specify some additional
writable directories - how are the symlinks created? What tells it
what to create and how to create them? Also, pretend I mounted a NFS
share (or block device, or whatever - just something that is not the
OS and is designed for storage of data) at /blah - would I be able to
write to /blah? (I haven't quite tried this yet)