Changes between Version 15 and Version 16 of BepFile

Timestamp:

10/08/10 14:11:48 (5 years ago)

Author:

scottmc

Comment:

added TEST key

BepFile

@@ -79 +79 @@
 ||{{{BUILD}}}||list of shell commands (script) to execute in order to build the port||shell||shell commands||no||-||
 ||{{{INSTALL}}}||list of shell commands to execute in order to install the port||shell||shell commands||no||-||
+||{{{TEST}}}||list of shell commands to execute the test(s) for the port||shell||shell commands||no||-||
 ||{{{LICENSE}}}||(list of) license(s) for the port||single, list||text||no||-||
 ||{{{COPYRIGHT}}}||(list of) copyright(s) for the port||single, list||text||no||-||
 
-BUILD and INSTALL scripts are plain bash shell scripts. It is possible to do conditional execution or even loops. For example, it is possible to distinguish between the different BeOS platforms using the {{{BEPORTS_PLATFORM}}} environment variable. It can be one of {{{R5}}}, {{{BONE}}} or {{{HAIKU}}}. Haikuporter detects which BeOS platform it is running on and set the {{{BEPORTS_PLATFORM}}} variable accordingly.
+BUILD, INSTALL and TEST scripts are plain bash shell scripts. It is possible to do conditional execution or even loops. For example, it is possible to distinguish between the different BeOS platforms using the {{{BEPORTS_PLATFORM}}} environment variable. It can be one of {{{R5}}}, {{{BONE}}} or {{{HAIKU}}}. Haikuporter detects which BeOS platform it is running on and set the {{{BEPORTS_PLATFORM}}} variable accordingly.
 
 An example of a build script is shown below. Notice that it is possible to add comments using a {{{#}}}. It is highly recommended to document anything special you might do inside a BUILD or INSTALL script. This might help people when they are porting other applications.