Research for app purchases

[Alexander Larsson]

On Tue, Oct 15, 2019 at 12:00 PM Alexander Larsson <alexl at redhat.com> wrote:
>
> But, we could add to the ostree-metadata info the commit ids, and then
> we could use that when available for the resolve operation, not having
> to download each individual commit if the version we're pulling (which
> we know from the partial summit) matches the one in the
> ostree-metadata. This seems like a useful optimization at the very
> least.
>
> I can still imagine cases where it would fail though. For example if
> you had contact with the master repo at some point and updated the
> ostree-metadata branch, but now you only have contact with a p2p
> mirror that has an older ostree-metadata version. We would only be
> able to install the mirrored version of a ref if it happened to match
> what was the current commit when you talked to the master repo. Maybe
> this limitation is fine for the case of purchased refs though?
> Opinions? Ideas?

I implemented this in https://github.com/flatpak/flatpak/pull/3167 and
it seems workable. The code will still download the commits if
necessary though, but we could conceptually drop a chunk of the change
in the PR if we enforce the use of ostree-metadata resolves for the
purchases.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                Red Hat, Inc
       alexl at redhat.com         alexander.larsson at gmail.com