On 05/09/16 at 01:34pm, Simon Fels wrote: > On 05.09.2016 13:31, Jamie Bennett wrote: > > On 05/09/16 at 07:06pm, Stuart Bishop wrote: > >> On 5 September 2016 at 18:08, David Callé <[email protected]> > >> wrote: > >> > >> > >> > License files can be copied across if they are present in the setup/ > >> > directory. Reproduced from docs/meta.md > >> > > >> > " > >> > ## Fixed assets > >> > > >> > Some metadata is provided in the form of conventions, such as license > >> files, > >> > icons and desktop files among others. For these fixed files to make > >> it > >> into > >> > your final snap they need to be in a `setup` directory at the same > >> level > >> of > >> > your `snapcraft.yaml`. > >> > " > >> > > >> > Of course the website needs updating to reflect the new syntax (and > >> the > >> fact > >> > that icon e.t.c also uses the setup/ dir now). > >> > >> You can find these details in the docs here: > >> http://snapcraft.io/docs/build-snaps/metadata#fixed-assets > >> > >> > >> > >> 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. > > > > Just put the license in the setup/ directory and name it license.txt. > > What does this actually trigger? Is it detected by the store? Or is it > just shipped with the snap and then being available as part of $SNAP?
I don't know if it is used in the store, someone else with more knowledge will have to comment. > regards, > Simon Regards, Jamie. > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/snapcraft -- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
