Sugar Network/Recipe Specification: Difference between revisions

Line 168:

Tags give more context in which to place the activity. This is used to allow users to find activities more easily in the journal, the home view, etc.

=== [Source] ===

Section makes sense only while packaging 3rd party application.

'''source''' = <url>

Url to download sources tarball.

'''patch''' = <path-to-patch> [patch-level] [; ...]

Patch downloaded tarball.

=== [Buid] ===

Line 193:

Line 205:

Various options that make sense only on package developer side.

'''~~source~~''' = <~~web~~-~~url~~>

'''exec''' = <shell-command>

~~Web link~~ to ~~the sources tarball, if parameter is absent, exec from this section will be used to generate tarball~~.

How to bundle package. By default 0sugar just bundles entirely root directory excluding temporary files.

'''requires''' = <dependency> [(=|>=|<) <version>] [; ...]

What packages should present before invoking ~~{{Code|0sugar dist}} command i.e. only in maintainer environment not even while building package from sources on user side or on OBS.~~

What packages should present before invoking ''exec'' command. For example if ''exec'' command generates .c files from .vala, vala dependency should be mentioned in ''requires'' option.

'''~~patch~~'~~'' = <path-to-patch> [patch-level] [; .~~..]

~~Patch downloaded tarball, makes sense only~~ if ~~source parameter exists. Option~~ ''exec'' ~~should present as well to make new tarball.~~

~~'''exec''' = <shell-~~command>

~~How to bundle package~~.

~~Shell command, executed~~ from ~~package root directory~~. ~~If this command starts to get complicated~~, ~~you~~ should ~~move it to a script and just set this attribute to the command to run the script. By default 0sugar just bundle entirely package directory excluding temporary files. If source parameter exists~~ in ~~this section, command will be executed within extracted directory of downloaded tarball~~.

== Glob patterns ==

@@ Line 168: / Line 168: @@
 Tags give more context in which to place the activity. This is used to allow users to find activities more easily in the journal, the home view, etc.
+=== [Source] ===
+Section makes sense only while packaging 3rd party application.
+ '''source''' = <url>
+Url to download sources tarball.
+ '''patch''' = <path-to-patch> [patch-level] [; ...]
+Patch downloaded tarball.
 === [Buid] ===
@@ Line 193: / Line 205: @@
 Various options that make sense only on package developer side.
-  '''source''' = <web-url>
+  '''exec''' = <shell-command>
-Web link to the sources tarball, if parameter is absent, exec from this section will be used to generate tarball.
+How to bundle package. By default 0sugar just bundles entirely root directory excluding temporary files.
   '''requires''' = <dependency> [(=|>=|<) <version>] [; ...]
-What packages should present before invoking {{Code|0sugar dist}} command i.e. only in maintainer environment not even while building package from sources on user side or on OBS.
+What packages should present before invoking ''exec'' command. For example if ''exec'' command generates .c files from .vala, vala dependency should be mentioned in ''requires'' option.
- '''patch''' = <path-to-patch> [patch-level] [; ...]
-Patch downloaded tarball, makes sense only if source parameter exists. Option ''exec'' should present as well to make new tarball.
- '''exec''' = <shell-command>
-How to bundle package.
-Shell command, executed from package root directory. If this command starts to get complicated, you should move it to a script and just set this attribute to the command to run the script. By default 0sugar just bundle entirely package directory excluding temporary files. If source parameter exists in this section, command will be executed within extracted directory of downloaded tarball.
 == Glob patterns ==