Re: libostree v2017.3

[Colin Walters <walters verbum org>]

On Fri, Mar 10, 2017, at 02:37 PM, Richard Hughes wrote:

>  * Pull the updates during the refresh phase (done when the session is idle)
>  * Deploy the updates on demand in the updates panel

Note that what I'm talking about here is for the *host* ostree case.
The core libostree has always supported pulling without deploying, though
libflatpak (FlatpakInstallation looks like) is another layer.

> What I don't know how to do is show some changelog-style update notes
> for the pending deploy. Ideas welcome. Thanks.

Yeah, though this is one of those things where the build/server and client side
libraries and the user interface all end up tied together.  You get into
deep questions like is each commit in the repo a distinct release?  Do you
show intermediate commits?  What's putting data into the commits and
how is it formatted?

Right now I see e.g.:

```
ostree --repo=/var/lib/flatpak/repo log org.gnome.Builder-origin:appstream/x86_64
commit 2b73c4d80be6edc9fa3a4e7adfa1dcbeda0db858b60b5bad78ff418dab512ad3
Date:  2017-03-10 14:46:52 +0000

    Update

```

I'm definitely interested in a discussion around these things, since I
want to do this type of thing for rpm-ostree as well.  Particularly for
the server case, be able to aggregate CVE metadata from the originating
rpm-md repo: https://github.com/projectatomic/rpm-ostree/issues/113