Sugar Network/Recipe Specification: Difference between revisions
→[Activity]: more explicit "icon" usecase in actiivties |
No edit summary |
||
| Line 84: | Line 84: | ||
'''bundle_id''' = <bundle-id> | '''bundle_id''' = <bundle-id> | ||
Required. See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. | Required. See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. This option is deprecated, use ''sweet'' instead, but it should still be present to not fail in current sugar. | ||
'''icon''' = <icon-file-name-without-suffix> | '''icon''' = <icon-file-name-without-suffix> | ||
Required. Behaviour from {{Code|activity.info}} is supported (value should not have {{Code|.svg}} suffix, and icon file can be found only in {{Code|activity}} subdirectory) and deprecated | Required. Behaviour from {{Code|activity.info}} is supported (value should not have a {{Code|.svg}} suffix, and the icon file can be found only in the {{Code|activity}} subdirectory) and, while deprecated, it needs to be used to not break backwards compatibility. For the remaining cases, the regular ''icon'' behaviour should be used instead. | ||
'''exec''' = <shell-command> | '''exec''' = <shell-command> | ||
| Line 198: | Line 198: | ||
'''exec''' = <shell-command> | '''exec''' = <shell-command> | ||
Optional. Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing the ''exec'' shell command, {{Code|sweets}} will pick up newly appearing tarball if it was created in the sweet root directory. | Optional. Execute an external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing the ''exec'' shell command, {{Code|sweets}} will pick up a newly appearing tarball if it was created in the sweet root directory. | ||
'''include''' = <glob-pattern> [; ...] | '''include''' = <glob-pattern> [; ...] | ||