Re: [BuildStream] plugin as elements

[Tristan Van Berkom <tristan vanberkom codethink co uk>]

Hi,

Let me correct my oversnip here ;-)

On Mon, 2020-04-27 at 18:38 +0900, Tristan Van Berkom wrote:
> Hi Benjamin,
[...]
> My rationale for the above is that on the one hand, we would want to
> use defaults laid out from the project where the plugin will be used,
> this does seem desirable.

...

> I decided to delete the following three omitted paragraphs from this
> email.

Looks like I omitted the "other hand" from the above statement with my
overzealous snip...

The other hand to the above is that plugins (with default YAML) loaded
from one project will most probably have variables to expand, and it is
even possible for them to try to override or append/prepend to lists in
default configuration.

This raises the whole question about whether a plugin originating from
a foreign junctioned project can safely be loaded against a set of
defaults which that plugin is unfamiliar with.

This of course raises similar questions about default YAML in plugins
which do not even come with project.conf defaults, such as pip provided
plugins... and I think this is especially significant now that Jürg was
speaking of making the base project.conf "barebones" and removing most
of the default variables from there.

Sorry for leaving this (rather significant) context out of my previous
reply.

Cheers,
    -Tristan