Re: Redistributing refs from multiple origins in a single repository

[Colin Walters <walters verbum org>]

On Wed, Jun 7, 2017, at 01:16 PM, Philip Withnall wrote:
> Correct, this is all verify-and-trust-on-first-use. If we later add the
> official gnome-apps, we’ll end up in the situation where two locally
> configured remotes have the same origin ID. That’s not something I want
> to disallow (they might be the new and old locations for the content,
> for example), but it could potentially be used as a red flag that
> something a bit odd is going on. I think that’s something to explore in
> future.

Broadly speaking we've been talking about a model where
*after* the user has a given (collection id, ref) pair, they can update
that pair from any set of remotes that provide it.

But just to clarify something - we're not talking about doing anything
P2P/discovery for *new* ref installs?

Basically, `flatpak install` would still require a (remote, ref) pair?
Or are we scoping in here simply installing "ref" and having that
be discovered too and automatically bound to a remote if we happen
to have a remote available that provides it?