Sugar Network/Recipe Specification: Difference between revisions

Line 4:

== Spec file sections ==

The ~~0sugar~~.recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of Zero Sugar workflows, everything depends on the ~~0sugar~~.recipe spec file.

The sweets.recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of Zero Sugar workflows, everything depends on the sweets.recipe spec file.

For activities, activity.info, an inherited recipe file name, is supported.

Line 113:

'''exec''' = <shell-command>

Instead of using an executable program from the ''main'' option, ~~0sugar~~ can bundle a script to run an arbitrary shell command.

Instead of using an executable program from the ''main'' option, {{Code|sweets}} can bundle a script to run an arbitrary shell command.

If a package has neither ''main'' nor ''exec'', then it cannot be executed. This typically means that the package is for a library.

Line 173:

'''exec''' = <shell-command>

Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing ''exec'' shell command, ~~0sugar~~ will pick up newly appeared tarball if it was created in package root directory.

Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing ''exec'' shell command, {{Code|sweets}} will pick up newly appeared tarball if it was created in package root directory.

'''include''' = <glob-pattern> [; ...]

Line 200:

'''bundle_id''' = <bundle-id>

See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. Option will be deprecated after implementing ~~0sugar~~ in glucose and switching to identifying activities by urls (like 0install feeds).

See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. Option will be deprecated after implementing Zero Sugar in glucose and switching to identifying activities by urls (like 0install feeds).

'''icon''' = <icon-file-name-without-suffix>

@@ Line 4: / Line 4: @@
 == Spec file sections ==
-The 0sugar.recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of Zero Sugar workflows, everything depends on the 0sugar.recipe spec file.
+The sweets.recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of Zero Sugar workflows, everything depends on the sweets.recipe spec file.
 For activities, activity.info, an inherited recipe file name, is supported.
@@ Line 113: / Line 113: @@
   '''exec''' = <shell-command>
-Instead of using an executable program from the ''main'' option, 0sugar can bundle a script to run an arbitrary shell command.
+Instead of using an executable program from the ''main'' option, {{Code|sweets}} can bundle a script to run an arbitrary shell command.
 If a package has neither ''main'' nor ''exec'', then it cannot be executed. This typically means that the package is for a library.
@@ Line 173: / Line 173: @@
   '''exec''' = <shell-command>
-Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing ''exec'' shell command, 0sugar will pick up newly appeared tarball if it was created in package root directory.
+Execute external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command. After executing ''exec'' shell command, {{Code|sweets}} will pick up newly appeared tarball if it was created in package root directory.
   '''include''' = <glob-pattern> [; ...]
@@ Line 200: / Line 200: @@
   '''bundle_id''' = <bundle-id>
-See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. Option will be deprecated after implementing 0sugar in glucose and switching to identifying activities by urls (like 0install feeds).
+See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]]. Option will be deprecated after implementing Zero Sugar in glucose and switching to identifying activities by urls (like 0install feeds).
   '''icon''' = <icon-file-name-without-suffix>