5,705
edits
Changes
Sugar Network/Recipe Specification (view source)
Revision as of 10:56, 29 October 2011
, 10:56, 29 October 2011no edit summary
* testing
* testing
* stable
* stable
'''requires''' = <dependency> [; ...]
Optional. List of [[Platform_Team/Guide/Sweets_Packaging#Dependencies|dependencies]] that should exist at run-time before launching the sweet.
'''suggests''' = <dependency> [; ...]
Optional. List of [[Platform_Team/Guide/Sweets_Packaging#|Dependenciesdependencies]] that will be demanded to be present at run-time only if it was explicitly required from a user.
=== [Activity] ===
=== [Activity] ===
Optional. List of mime types supported by the activity. It's used when opening a file from the web, or to present to the user a list of activities that can open a certain Journal object.
Optional. List of mime types supported by the activity. It's used when opening a file from the web, or to present to the user a list of activities that can open a certain Journal object.
=== [Application] ===
=== [Application] ===
Required. The relative path of an executable command inside the implementation that should be executed by default when the sweet is run. Command can have optional arguments.
Required. The relative path of an executable command inside the implementation that should be executed by default when the sweet is run. Command can have optional arguments.
=== [Library] ===
=== [Library] ===
Required. The environment variables 0install should export to the process that uses this sweet.
Required. The environment variables 0install should export to the process that uses this sweet.
=== [Package] ===
=== [Package] ===
Required. The filename with sources bundle.
Required. The filename with sources bundle.
'''patches''' = <patch-filename> [patch-level] [; ...]
'''patches''' = <patch-filename> [patch-level] [; ...]
'''NOTE''' The commands in this section will be executed, not only in the developer's environment, but also in the user's, if a proper binary wasn't found; so move all development-related commands, like {{Code|autogen.sh}}, to the ''[Source]'' section.
'''NOTE''' The commands in this section will be executed, not only in the developer's environment, but also in the user's, if a proper binary wasn't found; so move all development-related commands, like {{Code|autogen.sh}}, to the ''[Source]'' section.
'''requires''' = <dependency-name> [(=|>=|<) <version>] [; ...]
'''requires''' = <dependency> [; ...]
Optional. This defines what [[Platform_Team/Guide/Sweets_Packaging#Interfaces|dependencies]] should be present before building the sweet from sources. Note that ''requires'' from [[#.5BComponent.5D|[Component]]] sections are not auto included in the build-time dependencies.
Optional. This defines what [[Platform_Team/Guide/Sweets_Packaging#Dependencies|dependencies]] should be present before building the sweet from sources. Note that ''requires'' from [[#.5BComponent.5D|[Component]]] sections are not auto included in the build-time dependencies.
'''clean''' = <shell-command>
'''clean''' = <shell-command>
Optional. If the ''exec'' option was not used, all files will be bundled and these [[Platform_Team/Guide/Sweets_Packaging#Glob_patterns|glob patterns]] might be used to reify the selection.
Optional. If the ''exec'' option was not used, all files will be bundled and these [[Platform_Team/Guide/Sweets_Packaging#Glob_patterns|glob patterns]] might be used to reify the selection.
'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
'''requires''' = <dependency> [; ...]
Optional. The dependencies that should be present before creating sources tarball. For example, if the ''exec'' command generates .c files from .vala, the vala dependency should be mentioned in the ''requires'' option.
Optional. The [[Platform_Team/Guide/Sweets_Packaging#Dependencies|dependencies]] that should be present before creating sources tarball. For example, if the ''exec'' command generates .c files from .vala, the vala dependency should be mentioned in the ''requires'' option.
== Predefined options ==
== Predefined options ==