Comment 3 for bug 1597603

El 30/06/16 a las 09:21, Kyle Fazzari escribió:
> Note that this functionality is documented here:
> https://github.com/snapcore/snapcraft/blob/master/docs/plugins.md
>
> The idea is to deal with the potential clash between snapcraft's plugins
> and local plugins:
>
> 1. If one names their plugin foo.py and refers to it as `foo` in the yaml, if snapcraft includes a foo.py plugin as well snapcraft's will be preferred.
> 2. If one names their plugin x-foo.py and refers to it as `foo` in the yaml, if snapcraft includes a foo.py plugin as well the local one will still be preferred.
>
> However, I agree that `x-*` is not intuitive, and I've never hit a
> situation where (1) was important functionality. My suggestion is to
> simply always prefer the local plugins upon clash, and get rid of the
> `x-*` prefix. Thoughts?

We went back and forth on this a lot. This is the original implementation, then we allowed only naming them x-foo which others found unintuitive, then we just went with no `x-` at all which had another camp confused.

The "x-" means not official, I don't mind readding x-foo as a plugin name, I would actually prefer that.