Sugar Network/Recipe Specification: Difference between revisions

Line 253:

[<component-name>]

...

~~The final ''[Service]'' implementation will contain tarball per component. All these tarballs will be unpacked to the same root directory.~~

Only followed options make sense for component sections and cannot be used in recipe section, other options recipe component section will inherit from recipe section:

Line 266:

Line 264:

* slots

For example having followed lines and invoking ''0sugar build'' on two platforms - x86 and x86_64 platforms, two (per arch) implementations will be created and they will use three tarballs - x86 and x86_64 tarballs from ''[binary]'' section and one common for both implementations ''[data]'' tarball.

The same component could a part of different recipes. In that case, different (sub)service implementations will contain the same component tarball.

The final ''[Service]'' implementation will contain tarball per component. All these tarballs will be unpacked to the same root directory. For example having followed lines and invoking ''0sugar build'' on two platforms - x86 and x86_64 platforms, two (per arch) implementations will be created and they will use three tarballs - x86 and x86_64 tarballs from ''[binary]'' section and one common for both implementations ''[data]'' tarball.

[Service]

@@ Line 253: / Line 253: @@
    [<component-name>]
    ...
-The final ''[Service]'' implementation will contain tarball per component. All these tarballs will be unpacked to the same root directory.
 Only followed options make sense for component sections and cannot be used in recipe section, other options recipe component section will inherit from recipe section:
@@ Line 266: / Line 264: @@
 * slots
-For example having followed lines and invoking ''0sugar build'' on two platforms - x86 and x86_64 platforms, two (per arch) implementations will be created and they will use three tarballs - x86 and x86_64 tarballs from ''[binary]'' section and one common for both implementations ''[data]'' tarball.
+The same component could a part of different recipes. In that case, different (sub)service implementations will contain the same component tarball.
+The final ''[Service]'' implementation will contain tarball per component. All these tarballs will be unpacked to the same root directory. For example having followed lines and invoking ''0sugar build'' on two platforms - x86 and x86_64 platforms, two (per arch) implementations will be created and they will use three tarballs - x86 and x86_64 tarballs from ''[binary]'' section and one common for both implementations ''[data]'' tarball.
   [Service]