5,705
edits
Changes
Jump to navigation
Jump to search
Line 106:
Line 106: − − '''main''' = <path-to-exec-file> − − For applications, the relative (from Zero Sugar based project) path to exec file. Doesn't make sense for packages like libraries. − Instead of using an executable program from the ''main'' option, 0sugar can bundle a script to run an arbitrary shell command.+ − − '''exec'''[<script-name>] = <shell-command> − − Also, 0sugar can bundle arbitrary shell scripts. It may be useful for a 0install distribution, e.g., to pass a path to an already-bundled command instead of using this command directly: − − binding = replace VALADIR, PATH − exec[valac] = exec "$VALADIR"/bin/valac --vapidir "$VALADIR"/share/vala/vapi "$@"
Sugar Network/Recipe Specification (view source)
Revision as of 11:52, 25 July 2010
, 11:52, 25 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.
'''exec''' = <shell-command>
'''exec''' = <shell-command>
For applications, using the relative (from Zero Sugar based project) path, run bundled executable file or just arbitrary shell command. Doesn't make sense for packages like libraries.
'''include''' = <glob-pattern> [; ...]
'''include''' = <glob-pattern> [; ...]