> The store treats it as if it were per snap, meaning that it lets a publisher unilaterally change the license of something, which is not ideal.
The license field is not authoritative, it reflects what license the code is under. The store allows the publisher to rectify mistakes, and update the license to reflect reality.
> The store treats it as if it were per snap, meaning that it lets a publisher unilaterally change the license of something, which is not ideal.
The license field is not authoritative, it reflects what license the code is under. The store allows the publisher to rectify mistakes, and update the license to reflect reality.
Note the discussion about license being per-revision or per-snap is best had on https:/ /forum. snapcraft. io/t/snap- license- metadata/ 856/52
I also believe that snapcraft *does* support license, but only when actually running 3.x code (i.e. base: keyword is present).