5,705
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − <noinclude> − </noinclude> − + − + Line 16:
Line 14: − + Line 266:
Line 264: − − Also, during the ''0sugar build'' command invocation, ''0sugar'' exports the environment variables that should be used in ''exec'' options, for example, to implement a conditional build. − − * ''ZSUGAR_<argument-in-upper-case>'' map ''0sugar'' long command line arguments − * ''SECTION_<section-name-in-upper-case>'' for every spec file section that will be processed
Sugar Network/Recipe Specification (view source)
Revision as of 23:23, 16 September 2010
, 23:23, 16 September 2010no edit summary
{{TOCright}}
{{TOCright}}
[[Category:Zero Sugar]]
[[Category:Zero Sugar]]
== Spec file sections ==
== Spec file sections ==
The 0sugar.info 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.info spec file.
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.
For activities, ''activity.info'', a deprecated spec file name, is supported.
For activities, activity.info, a inherited recipe file name, is supported.
=== [DEFAULT] ===
=== [DEFAULT] ===
'''import''' = <filename> [; ...]
'''import''' = <filename> [; ...]
Import another spec file. Makes sense only within the [DEFAULT] section itself.
Import another recipe file. Makes sense only within the [DEFAULT] section itself.
=== Common options ===
=== Common options ===
* ''LANG'' current language while building per language implementation
* ''LANG'' current language while building per language implementation
== Examples ==
== Examples ==