5,705
edits
Changes
Jump to navigation
Jump to search
Line 106:
Line 106: + + + + − For applications, using the relative (from Zero Sugar based project) path, run packaged executable file or just arbitrary shell command. Doesn't make sense for packages like libraries.+
Sugar Network/Recipe Specification (view source)
Revision as of 03:07, 28 July 2010
, 03:07, 28 July 2010→[Package]
The environment variables 0install should export to the process that uses this package. This makes sense only for multiple-activity-serving dependencies (like libraries), not for the activity itself.
The environment variables 0install should export to the process that uses this package. This makes sense only for multiple-activity-serving dependencies (like libraries), not for the activity itself.
'''main''' = <path-to-exec-file>
The relative path of an executable inside the implementation that should be executed by default when the package is run.
'''exec''' = <shell-command>
'''exec''' = <shell-command>
Instead of using an executable program from the ''main'' option, 0sugar can bundle a script to run an arbitrary shell command. If a package has no ''main'' and ''exec'' settings, then it cannot be executed. This typically means that the package is for a library.
'''include''' = <glob-pattern> [; ...]
'''include''' = <glob-pattern> [; ...]