<div dir="ltr">On 5 September 2016 at 18:08, David Callé <span dir="ltr"><<a href="mailto:david.calle@canonical.com" target="_blank">david.calle@canonical.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> License files can be copied across if they are present in the setup/<br>
> directory. Reproduced from docs/<a href="http://meta.md" rel="noreferrer" target="_blank">meta.md</a><br>
><br>
> "<br>
> ## Fixed assets<br>
><br>
> Some metadata is provided in the form of conventions, such as license files,<br>
> icons and desktop files among others. For these fixed files to make it into<br>
> your final snap they need to be in a `setup` directory at the same level of<br>
> your `snapcraft.yaml`.<br>
> "<br>
><br>
> Of course the website needs updating to reflect the new syntax (and the fact<br>
> that icon e.t.c also uses the setup/ dir now).<br>
<br>
</span>You can find these details in the docs here:<br>
<a href="http://snapcraft.io/docs/build-snaps/metadata#fixed-assets" rel="noreferrer" target="_blank">http://snapcraft.io/docs/<wbr>build-snaps/metadata#fixed-<wbr>assets</a></blockquote><div><br><br></div><div>This does not mention the magic name(s) needed for license (nee licence, copyright, legal, copying etc.) files to be discovered and made available from the snap metadata by installers, the snap store or other consumers. Which is what we are really asking. <br clear="all"></div></div><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Stuart Bishop <<a href="mailto:stuart.bishop@canonical.com" target="_blank">stuart.bishop@canonical.com</a>></div>
</div></div>