Sugar Network/Recipe Specification: Difference between revisions

Line 187:

How to build binaries. If package contains binary implementations, this section should be present to describe the building process.

'''NOTE''' This section commands will be executed not only in the developer's environment but also in the user's, if a proper binary wasn't found; so move all development-related commands, like autogen.sh, to ''[Maintain]'' section.

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

Line 192:

Line 194:

What [[#Package_names|dependencies]] should be present before building the package from sources, in addition to ''requires'' values from ''[Package]'' sections.

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

'''configure''' = <shell-command>

~~How~~ to ~~build binaries~~.

Shell command to configure sources before building, e.g, invoking ''configure'' script in auto-tools based projects. It is important to use [[#Predefined_options|predefined constants]], like ''PREFIX'', during configuration to prepare valid Zero packages. If source code does not require configuration stage, this option could be omited.

~~Its value is a~~ shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.

'''build''' = <shell-command>

~~''NOTE'' This~~ command ~~will be executed~~ not ~~only in the developer's environment but also in the user's~~, ~~if a proper binary wasn't found; so do not use here any development-related commands like autogen~~.sh

Shell command to build binaries from sources. If source code does not require building stage, this option could be omited.

'''install''' = <shell-command>

~~How~~ to ~~install package~~.

Shell command should place files, that are ready for distribution, to ''%(DISTDIR)s'' directory.

=== [Maintain] ===

@@ Line 187: / Line 187: @@
 How to build binaries. If package contains binary implementations, this section should be present to describe the building process.
+'''NOTE''' This section commands will be executed not only in the developer's environment but also in the user's, if a proper binary wasn't found; so move all development-related commands, like autogen.sh, to ''[Maintain]'' section.
   '''requires''' = <dependency-name> [(=|>=|<) <version>] [; ...]
@@ Line 192: / Line 194: @@
 What [[#Package_names|dependencies]] should be present before building the package from sources, in addition to ''requires'' values from ''[Package]'' sections.
-  '''build''' = <shell-command>
+  '''configure''' = <shell-command>
-How to build binaries.
+Shell command to configure sources before building, e.g, invoking ''configure'' script in auto-tools based projects. It is important to use [[#Predefined_options|predefined constants]], like ''PREFIX'', during configuration to prepare valid Zero packages. If source code does not require configuration stage, this option could be omited.
-Its value is a shell command, executed inside the build directory $BUILDDIR. It must compile the source in $SRCDIR, putting the final result (ready for distribution) in $DISTDIR. If this command starts to get complicated, you should move it to a script (either inside the main source archive or in a separate dependency) and just set this attribute to the command to run the script.
+ '''build''' = <shell-command>
-''NOTE'' This command will be executed not only in the developer's environment but also in the user's, if a proper binary wasn't found; so do not use here any development-related commands like autogen.sh
+Shell command to build binaries from sources. If source code does not require building stage, this option could be omited.
   '''install''' = <shell-command>
-How to install package.
+Shell command should place files, that are ready for distribution, to ''%(DISTDIR)s'' directory.
 === [Maintain] ===