Difference between revisions of "Sugar Network/Recipe Specification"

From Sugar Labs
Jump to navigation Jump to search
 
(26 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
The recipe specification file is an analog of scenario files in regular GNU/Linux distributions, like .spec files in RPM. It is the cornerstone of [[Platform_Team/Sugar_Doers_Kit|SDK]], everything on sweet project level depends on the recipe file. For activities, {{Code|activity/activity.info}}, an inherited recipe file name, is supported.
+
== Summary ==
  
−
== Recipe structure ==
+
The document describes software specification files format which is a superset on top of the Sugar [[Development_Team/Almanac/Activity_Bundles|activity bundles]] specification. This format is backwards compatible with [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info]] files to make sure that software starts well from the regular Sugar Shell. But the major purpose of introducing new format is supporting software hosted on the [[Sugar Network]]. In particular, new format assumes the following functionality:
  
−
Recipe file is an [http://docs.python.org/library/configparser.html ini] format configuration file that might consist of several sections:
+
* Support binary based software;
 +
* Provide information about software dependencies;
 +
* Introduce stability levels to make it possible (for interested in people) to run development versions using the same, like for stable releases, distribution channel;
 +
* Distribute not only Sugar activities, e.g., software libraries;
 +
* Include all required information to make it possible to reuse the same spec file on different software evolution phases, like, making sources tarball, building binaries on Sugar Labs [[Platform_Team/Open_Build_Service|instance]] of the [http://openbuildservice.org/ Open Build Service], executing.
  
−
* One or more [[#Use case sections|use case sections]].
+
The format is partially based on the [http://0install.net/ Zero Install] [http://0install.net/interface-spec.html specification] since implementation code reuses Zero Install library in order to launch software on users side.
−
* Optional [[#Archive sections|archive sections]].
 
−
* Optional [[#Auxiliary sections|auxiliary sections]].
 
−
* Optional {{Code|[DEFAULT]}} section with common options that are accessible from all other sections.
 
  
−
== Use case sections ==
+
== Spec file locations ==
  
−
Recipe should contain at least one use case section to describe how the sweet might be used.
+
There are two possible spec file locations (staring from the top directory of a distribution bundle):
  
−
Use case sections are named:
+
* {{Code|/activity/activity.info}}<br>for Sugar activities to make them capable to be launched from the regular Sugar Shell;
 +
* {{Code|/sweets.recipe}}<br>in the rest of cases.
  
−
[''use-case-type''[:''sub-name'']]
+
== Configuration sections ==
  
−
Where ''use-case-type'' is one of the following sub sections and ''sub-name'' is an optional identifier used if there are more than one sections of the same type.
+
As ''activity.info'' files, new format is based on [[wikipedia:INI_file|INI files]] and should contain at least one of the following sections.
−
 
 
−
Regardless of the type, a use case section (or one of them) should contain the following options.
 
  
 
=== Common options ===
 
=== Common options ===
  
−
'''implement''' = <sweet> [; ...]
+
Regardless of the software type, a recipe section (or one of them) should contain the following options.
  
−
Required. The list of sweets current project is implementing.
+
<div id="context"></div>
  
−
  '''associate''' = <sweet> [; ...]
+
  '''context''' = ''GUID''
  
−
Optional. The list of sweets whose implementations might be considered as additional implementations for current one.
+
Required (but see the [[#.5BActivity.5D|[Activity]]] section). The value which uniquely identifies a software project this particular version implements. This is a Sugar Network [[Platform_Team/Sugar_Network/Objects_model|Context]] GUID.
  
−
'''name''' = <name>
+
<div id="name"></div>
  
−
Optional. Free-form name. (It is equal to the ''sweet'', by default.)
+
'''name''' = ''NAME''
  
−
'''summary''' = <one-line-description>
+
Optional. Free-form name. (It is equal to the ''implemented'', by default.)
  
−
Required. Short descriptive line.
+
<div id="summary"></div>
  
−
  '''description''' = <multi-line-description>
+
  '''summary''' = ''ONE_LINE_TEXT''
  
−
Optional. Long descriptive text. To wrap long text, all lines starting from the second, should start with spaces. This field is equal to ''summary'' by default.
+
Required. Short descriptive line.
  
−
'''license''' = <license-name>
+
<div id="description"></div>
  
−
Required. The license. Short license names from [http://fedoraproject.org/wiki/Licensing Fedora naming scheme] are welcome.
+
'''description''' = ''MULTI_LINE_TEXT''
  
−
'''homepage''' = <url>
+
Optional. Long descriptive text. To wrap long text, all lines starting from the second, should start with spaces. This field is equal to ''summary'' by default.
  
−
Required. Sweet project home page.
+
<div id="license"></div>
  
−
  '''icon''' = <icon-file-name>
+
  '''license''' = ''LICENSE'' [; ...]
  
−
Optional. Path to the icon file starting from the path where the recipe file is located.
+
Required. Short license names. The licenses should conform with the [[Activity Library]] licensing [[Activity_Library/Editors/Policy/Licensing|policy]].
  
−
'''category''' = <category> [; ...]
+
<div id="homepage"></div>
  
−
Optional. A classification for the sweet using values defined by [http://standards.freedesktop.org/menu-spec/latest/apa.html freedesktop.org menu specification].
+
'''homepage''' = ''URL''
  
−
'''tags''' = <tag> [; ...]
+
Required. Software project home page.
  
−
Optional. Tags give more context in which to group the sweet. This is used to allow users to find sweets more easily.
+
<div id="icon"></div>
  
−
  '''version''' = <version-number>
+
  '''icon''' = ''FILENAME''
  
−
Required. Current version of the sweet using [http://0install.net/interface-spec.html#id4016582 0install version format].
+
Optional (but see the [[#.5BActivity.5D|[Activity]]] section). Path to the icon file starting from the path where the recipe file is located.
  
−
'''stability''' = <stability-level>
+
<div id="tags"></div>
  
−
Required. Stability level of the current version. Values conform to [http://0install.net/interface-spec.html#id4016716 0install stability levels] and could be:
+
'''tags''' = ''TAG'' [; ...]
−
* insecure
 
−
* buggy
 
−
* developer
 
−
* testing
 
−
* stable
 
  
−
=== [Activity] ===
+
Optional. Tags give more context by which to group the software. This is done to allow users to make search more easily.
  
−
This section type should be present only in activities.
+
<div id="version"></div>
  
−
  '''activity_version''' = <version>
+
  '''version''' = ''VERSION''
  
−
Deprecated, use ''version'' instead. Should be still present only to run the activity in non-sweets environment. It will be useful to use expansion like {{Code|%(version)s}} for this option.
+
Required. Current version of the software using [[#Version_numbers|special notation]]. Note, to make Sugar activity bundles compatible with pristine Sugar, use a limited format subset supported by the Sugar Shell.
  
−
'''bundle_id''' = <bundle-id>
+
<div id="stability"></div>
  
−
Deprecated. Should be still present only to run the activity in non-sweets environment. See [[Development_Team/Almanac/Activity_Bundles#.info_file_format|activity.info file specification]].
+
'''stability''' = ''LEVEL''
  
−
'''icon''' = <icon-file-name-without-suffix>
+
Required. Stability level of the current version. Values conform to the [[#Software_stability_levels|below list]].
  
−
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.
+
<div id="requires"></div>
  
−
  '''exec''' = <shell-command>
+
  '''requires''' = ''DEPENDENCY'' [; ...]
  
−
Required. Sugar will pass additional [[Development_Team/Low-level_Activity_API#Command_Line_Arguments| command line arguments]] to this command.
+
Optional. List of [[#Dependencies|dependencies]] that should exist at run-time before launching the release.
  
−
'''mime_types''' = <mime-type> [; ...]
+
=== [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.
+
This section type should be present only in Sugar activities.
  
−
'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
+
<div id="activity_version"></div>
  
−
Optional. List of [[Platform_Team/Guide/Packaging#Package_names|dependencies]] that should exist in run-time before launching the activity.
+
'''activity_version''' = ''VERSION''
  
−
=== [Application] ===
+
Required. An alias of the ''version'' option.
  
−
Application to run out of Sugar Shell.
+
<div id="bundle_id"></div>
  
−
  '''exec''' = <shell-command>
+
  '''bundle_id''' = ''BUNDLE_ID''
  
−
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. An alias of the ''context'' option.
  
−
'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
+
<div id="icon"></div>
  
−
Optional. List of [[Platform_Team/Guide/Packaging#Package_names|dependencies]] that should exist in run-time before launching the application.
+
'''icon''' = ''FILENAME_WITHOUT_SUFFIX''
  
−
=== [Library] ===
+
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.
  
−
'''binding''' = [prepend|append|replace] <variable-name> [<insert-text-to-prepend-variable-value>] [; ...]
+
<div id="activity_exec"></div>
  
−
Required. The environment variables 0install should export to the process that uses this sweet.
+
'''exec''' = ''SHELL_COMMAND''
  
−
'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
+
Required. Sugar will pass additional [[Development_Team/Low-level_Activity_API#Command_Line_Arguments| command line arguments]] to this command.
  
−
Optional. List of [[Platform_Team/Guide/Packaging#Package_names|dependencies]] the library is based on.
+
<div id="mime_types"></div>
  
−
=== [Package] ===
+
'''mime_types''' = ''MIME_TYPE'' [; ...]
  
−
This is a special section that does not relate to sweets directly and mentioned here only for recipe specification completeness. Using this section turns a recipe to some kind of meta-distribution spec file. The important things need to be kept in mind in that case:
+
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.
  
−
* it is very limited, in comparing with regular GNU/Linux distribution spec files, by design;
+
<!--
−
* there are no any intentions to follow meta-distribution way;
+
=== [Application] ===
−
* the major distribution way for sweets is using 0install, i.e., not using ''[Package]'' section, thus, native packages at all;
 
−
* this section was introduced only for cases when having native packages makes sense, e.g., for Live Sugar distributions or LTSP.
 
  
−
'''source''' = <filename>
+
Application to run outside of Sugar Shell.
  
−
Required. The filename with sources bundle.
+
'''exec''' = ''SHELL_COMMAND''
  
−
'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
+
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.
  
−
Optional. List of [[Platform_Team/Guide/Packaging#Package_names|dependencies]] the package is based on.
+
=== [Library] ===
  
−
  '''patches''' = <patch-filename> [patch-level] [; ...]
+
  '''binding''' = [prepend|append|replace] <variable-name> [<insert-text-to-prepend-variable-value>] [; ...]
  
−
The list of patches that need to be applied before building.
+
Required. The environment variables 0install should export to the process that uses this sweet.
 +
-->
 +
=== [Archive] ===
  
−
'''conflict''' = <native-package-name> [; ...]
+
This configuration section makes sense only while building binary distribution bundles from the sources. The section is optional for spec files that describe software assumed to be launched as-is, e.g., ''.xo'' bundles.
  
−
The list of native packages, i.e., names from particular GNU/Linux distribution, that conflict with the sweet based package and cannot be installed at the same time.
+
Each ''[Archive]'' section describes one particular binary bundle. There are might be several sections to define binaries for different cases:
  
−
== Archive sections ==
+
* To save storage space or bandwidth when some bundles will contain any-arch data that are common for all platforms, and another bundle will contain binaries for a particular platform;
 +
* Per language bundles, e.g., for media content.
  
−
Archive section describes the tarball that will contain the sweet implementation.
+
All archive sections are named:
  
−
If there are not any archive sections, the sweet implementation consists of only one archive that includes the entire {{Code|%(DESTDIR)s}} directory (excluding temporary files). At the same time, the sweet implementation might be split into several archives.
+
Archive[:''SUBNAME'']
  
−
Possible use cases:
+
And contain the following options:
  
−
* To save storage space or bandwidth when some tarballs will contain any-arch data that are common for all platforms, and another tarball will contain binaries for a particular platform.
+
<div id="archive-include"></div>
  
−
All archive sections are named:
+
'''include''' = ''GLOB'' [; ...]
  
−
[Archive[:''sub-name'']]
+
Optional. [[#Glob_patterns|Glob pattern]] for files to include in the archive. By default, all files are assumed.
  
−
And contain the following options:
+
<div id="archive-exclude"></div>
  
−
  '''include''' = <glob-pattern> [; ...]
+
  '''exclude''' = ''GLOB'' [; ...]
−
 
 
−
Optional. [[Platform_Team/Guide/Packaging#Glob patterns|Glob pattern]] for files to include in the archive. Path related patterns will be processed starting from the [[#Predefined_options|%(DISTDIR)s/%(PREFIX)s]] directory. By default, all files are assumed.
 
−
 
 
−
'''exclude''' = <glob-pattern> [; ...]
 
  
 
Optional. Like the ''include'' option, but used for excluding files from the archive. In addition, various temporary files will be excluded, like ''.bak'' or ''.pyc''.
 
Optional. Like the ''include'' option, but used for excluding files from the archive. In addition, various temporary files will be excluded, like ''.bak'' or ''.pyc''.
−
 
+
<!-- Not yet implemented
 
  '''langs''' = <lang-name> [; ...]
 
  '''langs''' = <lang-name> [; ...]
 
  include[<lang-name>] = <glob-pattern> [; ...]
 
  include[<lang-name>] = <glob-pattern> [; ...]
 
  exclude[<lang-name>] = <glob-pattern> [; ...]
 
  exclude[<lang-name>] = <glob-pattern> [; ...]
  
−
Optional. A special form of ''include''/''exclude'' options that are intended to create separate, per locale, archives. If a language is mentioned in the ''langs'' list, but doesn't have any ''include[]''/''exclude[]'' options, ''include''/''exclude'' will be used (in that case, using the special [[#Predefined_options|LANG]] variable makes sense).
+
Optional. A special form of ''include''/''exclude'' options that are intended to create separate, per locale, archives. If a language is mentioned in the ''langs'' list, but doesn't have any ''include[]''/''exclude[]'' options, ''include''/''exclude'' will be used (in that case, using the special [[#Predefined_constants|LANG]] constant makes sense).-->
  
−
  '''arch''' = <arch>
+
<div id="arch"></div>
 +
 
 +
  '''arch''' = ''ARCH''
  
 
Optional. Makes sense only for binary archives, and can contain:
 
Optional. Makes sense only for binary archives, and can contain:
−
* ''all'' for noarch (by default)
 
−
* ''any'' for binaries to use the current architecture
 
  
−
== Auxiliary sections ==
+
* ''all'' for noarch (by default),
−
 
+
* ''any'' for binaries to use the current architecture.
−
Sections that don't describe recipe components.
 
  
 
=== [Build] ===
 
=== [Build] ===
  
−
This section is required if the sweet needs additional work in order to prepare a ready-to-use installation. To prepare valid sweets, it is important to use [[#Predefined_options|predefined constants]] for options that contain shell commands. All shell commands will be executed from the {{Code|%(BUILDDIR)s}} directory.
+
This section is required if software needs additional work in order to prepare a ready-to-use installation. It is important to use [[#Predefined_constants|predefined constants]] for options that contain shell commands. All shell commands will be executed from the {{Code|%(BUILDDIR)s}} directory.
  
 
'''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>] [; ...]
+
<div id="build-requires"></div>
  
−
Optional. This defines what [[Platform_Team/Guide/Packaging#Package_names|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.
+
'''requires''' = ''DEPENDENCY'' [; ...]
  
−
  '''clean''' = <shell-command>
+
Optional. This defines what [[#Dependencies|dependencies]] should be present before building the software from sources. Note that common ''requires'' option values are not auto included in the build-time dependencies.
 +
 
 +
<div id="clean"></div>
 +
 
 +
  '''clean''' = ''SHELL_COMMAND''
  
 
Optional. Cleanup build environment before running ''configure'' command.
 
Optional. Cleanup build environment before running ''configure'' command.
  
−
  '''configure''' = <shell-command>
+
<div id="configure"></div>
 +
 
 +
  '''configure''' = ''SHELL_COMMAND''
  
 
Optional. Shell command to configure sources before building, e.g., invoking the configure script in auto-tools-based projects. If the source code does not require a configuration stage, this option could be omitted.
 
Optional. Shell command to configure sources before building, e.g., invoking the configure script in auto-tools-based projects. If the source code does not require a configuration stage, this option could be omitted.
  
−
  '''make''' = <shell-command>
+
<div id="build-make"></div>
 +
 
 +
  '''make''' = ''SHELL_COMMAND''
  
 
Optional. Shell command to make binaries from sources. If the source code does not require a making stage, this option could be omitted.
 
Optional. Shell command to make binaries from sources. If the source code does not require a making stage, this option could be omitted.
  
−
  '''install''' = <shell-command>
+
<div id="install"></div>
 +
 
 +
  '''install''' = ''SHELL_COMMAND''
  
 
Required. Shell command to place files that are ready for distribution into the {{Code|%(DESTDIR)s}} directory. If ''install'' is missing, the entire {{Code|%(BUILDDIR)s}} (excepting temporary files) will be copied.
 
Required. Shell command to place files that are ready for distribution into the {{Code|%(DESTDIR)s}} directory. If ''install'' is missing, the entire {{Code|%(BUILDDIR)s}} (excepting temporary files) will be copied.
Line 220: Line 221:
 
=== [Source] ===
 
=== [Source] ===
  
−
  '''exec''' = <shell-command>
+
The section makes sense only while building sources bundles and is a replacement of former ''MANIFEST'' file in Sugar activity bundles.
 +
 
 +
<div id="source-exec"></div>
 +
 
 +
  '''exec''' = ''SHELL_COMMAND''
 +
 
 +
Optional. Execute an external program to create sources tarball. Option might be used, e.g., to run {{Code|make dist}} command.
 +
 
 +
<div id="source-include"></div>
  
−
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'' [; ...]
 +
'''exclude''' = ''GLOB'' [; ...]
  
−
'''include''' = <glob-pattern> [; ...]
+
Optional. If the ''exec'' option was not used, all files will be bundled and these [[#Glob_patterns|glob patterns]] might be used to reify the selection.
−
'''exclude''' = <glob-pattern> [; ...]
 
  
−
Optional. If the ''exec'' option was not used, all files will be bundled and these [[Platform_Team/Guide/Packaging#Glob patterns|glob patterns]] might be used to concretize the selection.
+
<div id="source-requires"></div>
  
−
  '''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 [[#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 constants ===
  
−
Options defined within ''[Build]'' section:
+
Constants defined within the ''[Build]'' section:
  
 
* ''BUILDDIR'' where the build happens, directory contains un-tarred sources bundle. This variable can be used in ''binding'' options as well. During the local build, it will point environment variables to the root of sources directory.
 
* ''BUILDDIR'' where the build happens, directory contains un-tarred sources bundle. This variable can be used in ''binding'' options as well. During the local build, it will point environment variables to the root of sources directory.
Line 247: Line 256:
 
* ''LANG'' current language while building per language implementation
 
* ''LANG'' current language while building per language implementation
  
−
== Examples ==
+
== Version numbers ==
 +
 
 +
A version number string has the following form:
 +
 
 +
Version := DottedList ("-" Modifier? DottedList?)*
 +
DottedList := (Integer ("." Integer)*)
 +
Modifier := "pre" | "rc" | "post"
 +
 
 +
Numerically, the modifiers come in the order "-pre" (pre-release), "-rc" (release candidate), "-" (no modifier name), "-post" (post-release or patch level). Versions are ordered like this:
 +
 
 +
0.1
 +
1
 +
1.0
 +
1.2-pre
 +
1.2-pre1
 +
1.2-rc1
 +
1.2
 +
1.2-0
 +
1.2-post
 +
1.2-post1-pre
 +
1.2-post1
 +
1.2.1-pre
 +
1.2.1.4
 +
1.2.2
 +
1.2.10
 +
3
 +
 
 +
== Software stability levels ==
 +
 
 +
The spec file also gives a stability rating for each implementation. The following levels are allowed (must be lowercase in the feed files):
 +
 
 +
* ''stable'',
 +
* ''testing'',
 +
* ''developer'',
 +
* ''buggy'',
 +
* ''insecure''.
 +
 
 +
Stability ratings are expected to change over time. When any new release is made, its stability should be set to testing. Users who have selected Help test new versions will then start using it. Other users will continue with the previous stable release. After a while (days, weeks or months, depending on the project) with no serious problems found, the implementation's stability can be changed to stable so that everyone will use it.
 +
 
 +
If problems are found, it can instead be marked as ''buggy'', or ''insecure'' to avoid selecting these versions while launching on users side. ''developer'' is like a more extreme version of ''testing'', where the program is expected to have bugs.
 +
 
 +
When to use ''buggy''? Don't mark old releases as buggy every time you do a new release, just because a few bugs have been fixed. People who have selected network connectivity automatically pickup the new version anyway, so marking an older version as ''buggy'' only affects people who have explicitly stated that they don't want to use the latest version, but would prefer to use an older release to save network use.
 +
 
 +
== Dependencies ==
 +
 
 +
Dependencies might be used to declare software that the current release depends on.
  
−
=== Python activity ===
+
The format of a dependency string is:
  
−
Python-based activity with standard Sugar Platform dependencies.
+
''DEPENDENCY'' [(<|<=|=|>=|>) ''VERSION'']
  
−
[Activity]
+
The ''DEPENDENCY'' value is a GUID associated with dependency project, i.e., ''context'' value from dependency spec file. In general, it might be any software Sugar Network [http://node.sugarlabs.org/context Context], but current implementation assumes only GNU/Linux [http://node.sugarlabs.org/context?type=package packages].
−
implement = cartoon-builder
 
−
name      = Cartoon Builder
 
−
summary  = Create your own cell-animation sequences
 
−
license  = GPLv2+
 
−
homepage  = http://wiki.sugarlabs.org/go/Activities/Cartoon_Builder
 
−
 
−
version  = 11.4.9-pre3
 
−
stability = testing
 
−
 
−
icon      = activity-cartoonbuilder
 
−
exec      = sugar-activity activity.CartoonBuilderActivity
 
−
 
−
# Deprecated options to run activity in non-sweets environment
 
−
bundle_id = com.ywwg.CartoonBuilderActivity
 
−
activity_version = %(version)s
 
  
−
=== Python library ===
+
== Glob patterns ==
  
−
A python-based library that could be used as is, or as an activity dependency.
+
The ''include'' and ''exclude'' options contain file patterns. A pattern could be of two types:
  
−
[Library]
+
* doesn't contain ''/'' or ''**'' substrings, will be applied only to file names
−
implement = libjournal
+
* contains ''/'' or ''**'' substring, will be applied to the full file path (relative to the root), thus could affect several directory levels
−
name      = libjournal
 
−
summary  = Hight level library to create your own Journal-like activity
 
−
license  = GPLv3+
 
−
homepage  = http://wiki.sugarlabs.org/go/Activity_Team/Services/Journal
 
−
version  = 1
 
−
stability = testing
 
−
requires  = toolkit
 
−
binding  = PYTHONPATH
 
  
−
=== C-based library ===
+
Only these pattern symbols are allowed:
  
−
[DEFAULT]
+
* ''*'' matches everything, except directory separator
−
depends  = glib; gconf; libgee >= 0.5; gtk+ >= 2.12; pango >= 1.20; librsvg
+
* ''?'' matches any single character, except directory separator
−
+
* ''**'' matches everything, including directory separator
−
[Library]
 
−
implement = polyol
 
−
name      = polyol
 
−
summary  = Intermediate level GObject based libraries for Sugar
 
−
description = Polyol is a set of libraries that are written in Vala.
 
−
            Libraries are intended to provide high-level C API to basic Sugar
 
−
            features including Gtk based user interface. Applications that are
 
−
            linked against Polyol, interact with sugar processes
 
−
            (like shell, datastore, etc.) via DBus.
 
−
license  = LGPLv3+
 
−
homepage  = http://wiki.sugarlabs.org/go/Activity_Team/Polyol
 
−
 
−
version  = 1
 
−
stability = testing
 
−
 
−
binding  = LD_LIBRARY_PATH lib
 
−
            PKG_CONFIG_PATH lib/pkgconfig
 
−
            VAPIDIR share/vala/vapi
 
−
requires  = %(depends)s
 
−
 
−
[Archive]
 
−
arch      = any
 
−
 
−
[Build]
 
−
requires  = %(depends)s; pkg-config; cmake; make; gcc-c
 
−
configure = cmake -D CMAKE_INSTALL_PREFIX=%(PREFIX)s
 
−
                  -D PYTHON_SITEDIR=%(PREFIX)s/python
 
−
                  -D COMPONENTS="collab;ds;env;gui;shell;toolkit"
 
−
                  -D BINDING=python
 
−
                  -D CMAKE_C_FLAGS:STRING="%(CFLAGS)s"
 
−
                  .
 
−
make      = make
 
−
install  = make DESTDIR=%(DESTDIR)s install
 

Latest revision as of 18:00, 3 July 2013

Summary

The document describes software specification files format which is a superset on top of the Sugar activity bundles specification. This format is backwards compatible with activity.info files to make sure that software starts well from the regular Sugar Shell. But the major purpose of introducing new format is supporting software hosted on the Sugar Network. In particular, new format assumes the following functionality:

  • Support binary based software;
  • Provide information about software dependencies;
  • Introduce stability levels to make it possible (for interested in people) to run development versions using the same, like for stable releases, distribution channel;
  • Distribute not only Sugar activities, e.g., software libraries;
  • Include all required information to make it possible to reuse the same spec file on different software evolution phases, like, making sources tarball, building binaries on Sugar Labs instance of the Open Build Service, executing.

The format is partially based on the Zero Install specification since implementation code reuses Zero Install library in order to launch software on users side.

Spec file locations

There are two possible spec file locations (staring from the top directory of a distribution bundle):

  • /activity/activity.info
    for Sugar activities to make them capable to be launched from the regular Sugar Shell;
  • /sweets.recipe
    in the rest of cases.

Configuration sections

As activity.info files, new format is based on INI files and should contain at least one of the following sections.

Common options

Regardless of the software type, a recipe section (or one of them) should contain the following options. 

context = GUID

Required (but see the [Activity] section). The value which uniquely identifies a software project this particular version implements. This is a Sugar Network Context GUID. 

name = NAME

Optional. Free-form name. (It is equal to the implemented, by default.) 

summary = ONE_LINE_TEXT

Required. Short descriptive line. 

description = MULTI_LINE_TEXT

Optional. Long descriptive text. To wrap long text, all lines starting from the second, should start with spaces. This field is equal to summary by default. 

license = LICENSE [; ...]

Required. Short license names. The licenses should conform with the Activity Library licensing policy. 

homepage = URL

Required. Software project home page. 

icon = FILENAME

Optional (but see the [Activity] section). Path to the icon file starting from the path where the recipe file is located. 

tags = TAG [; ...]

Optional. Tags give more context by which to group the software. This is done to allow users to make search more easily. 

version = VERSION

Required. Current version of the software using special notation. Note, to make Sugar activity bundles compatible with pristine Sugar, use a limited format subset supported by the Sugar Shell. 

stability = LEVEL

Required. Stability level of the current version. Values conform to the below list. 

requires = DEPENDENCY [; ...]

Optional. List of dependencies that should exist at run-time before launching the release.

[Activity]

This section type should be present only in Sugar activities. 

activity_version = VERSION

Required. An alias of the version option. 

bundle_id = BUNDLE_ID

Required. An alias of the context option. 

icon = FILENAME_WITHOUT_SUFFIX

Required. Behaviour from activity.info is supported (value should not have a .svg suffix, and the icon file can be found only in the 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

Required. Sugar will pass additional command line arguments to this command. 

mime_types = MIME_TYPE [; ...]

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.

[Archive]

This configuration section makes sense only while building binary distribution bundles from the sources. The section is optional for spec files that describe software assumed to be launched as-is, e.g., .xo bundles.

Each [Archive] section describes one particular binary bundle. There are might be several sections to define binaries for different cases:

  • To save storage space or bandwidth when some bundles will contain any-arch data that are common for all platforms, and another bundle will contain binaries for a particular platform;
  • Per language bundles, e.g., for media content.

All archive sections are named: 

Archive[:SUBNAME]

And contain the following options: 

include = GLOB [; ...]

Optional. Glob pattern for files to include in the archive. By default, all files are assumed. 

exclude = GLOB [; ...]

Optional. Like the include option, but used for excluding files from the archive. In addition, various temporary files will be excluded, like .bak or .pyc. 

arch = ARCH

Optional. Makes sense only for binary archives, and can contain:

  • all for noarch (by default),
  • any for binaries to use the current architecture.

[Build]

This section is required if software needs additional work in order to prepare a ready-to-use installation. It is important to use predefined constants for options that contain shell commands. All shell commands will be executed from the %(BUILDDIR)s directory.

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 autogen.sh, to the [Source] section. 

requires = DEPENDENCY [; ...]

Optional. This defines what dependencies should be present before building the software from sources. Note that common requires option values are not auto included in the build-time dependencies. 

clean = SHELL_COMMAND

Optional. Cleanup build environment before running configure command. 

configure = SHELL_COMMAND

Optional. Shell command to configure sources before building, e.g., invoking the configure script in auto-tools-based projects. If the source code does not require a configuration stage, this option could be omitted. 

make = SHELL_COMMAND

Optional. Shell command to make binaries from sources. If the source code does not require a making stage, this option could be omitted. 

install = SHELL_COMMAND

Required. Shell command to place files that are ready for distribution into the %(DESTDIR)s directory. If install is missing, the entire %(BUILDDIR)s (excepting temporary files) will be copied.

[Source]

The section makes sense only while building sources bundles and is a replacement of former MANIFEST file in Sugar activity bundles. 

exec = SHELL_COMMAND

Optional. Execute an external program to create sources tarball. Option might be used, e.g., to run make dist command. 

include = GLOB [; ...]
exclude = GLOB [; ...]

Optional. If the exec option was not used, all files will be bundled and these glob patterns might be used to reify the selection. 

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.

Predefined constants

Constants defined within the [Build] section:

  • BUILDDIR where the build happens, directory contains un-tarred sources bundle. This variable can be used in binding options as well. During the local build, it will point environment variables to the root of sources directory.
  • DESTDIR temporary path to place installed files before bundling them
  • PREFIX should be used as installation prefix path, e.g., for ./configure --prefix
  • CFLAGS default gcc CFLAGS
  • CXXFLAGS default gcc CXXFLAGS

In sections that contain a langs option:

  • LANG current language while building per language implementation

Version numbers

A version number string has the following form: 

Version := DottedList ("-" Modifier? DottedList?)*
DottedList := (Integer ("." Integer)*)
Modifier := "pre" | "rc" | "post"

Numerically, the modifiers come in the order "-pre" (pre-release), "-rc" (release candidate), "-" (no modifier name), "-post" (post-release or patch level). Versions are ordered like this: 

0.1
1
1.0
1.2-pre
1.2-pre1
1.2-rc1
1.2
1.2-0
1.2-post
1.2-post1-pre
1.2-post1
1.2.1-pre
1.2.1.4
1.2.2
1.2.10
3

Software stability levels

The spec file also gives a stability rating for each implementation. The following levels are allowed (must be lowercase in the feed files):

  • stable,
  • testing,
  • developer,
  • buggy,
  • insecure.

Stability ratings are expected to change over time. When any new release is made, its stability should be set to testing. Users who have selected Help test new versions will then start using it. Other users will continue with the previous stable release. After a while (days, weeks or months, depending on the project) with no serious problems found, the implementation's stability can be changed to stable so that everyone will use it.

If problems are found, it can instead be marked as buggy, or insecure to avoid selecting these versions while launching on users side. developer is like a more extreme version of testing, where the program is expected to have bugs.

When to use buggy? Don't mark old releases as buggy every time you do a new release, just because a few bugs have been fixed. People who have selected network connectivity automatically pickup the new version anyway, so marking an older version as buggy only affects people who have explicitly stated that they don't want to use the latest version, but would prefer to use an older release to save network use.

Dependencies

Dependencies might be used to declare software that the current release depends on.

The format of a dependency string is: 

DEPENDENCY [(<|<=|=|>=|>) VERSION]

The DEPENDENCY value is a GUID associated with dependency project, i.e., context value from dependency spec file. In general, it might be any software Sugar Network Context, but current implementation assumes only GNU/Linux packages.

Glob patterns

The include and exclude options contain file patterns. A pattern could be of two types:

  • doesn't contain / or ** substrings, will be applied only to file names
  • contains / or ** substring, will be applied to the full file path (relative to the root), thus could affect several directory levels

Only these pattern symbols are allowed:

  • * matches everything, except directory separator
  • ? matches any single character, except directory separator
  • ** matches everything, including directory separator
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Sugar_Network/Recipe_Specification&oldid=88603"