Changes between Version 10 and Version 11 of BepFile

Timestamp:

11/13/09 12:29:16 (6 years ago)

Author:

scottmc

Comment:

added DISTRO section, and more beporter to haikuporter cleanups

BepFile

@@ -3 +3 @@
 == Introduction ==
 
-A .bep file is a ''recipe'' that BePorter uses to fetch, patch, build and install a software package. It is an ASCII file that contains a list of keys with corresponding (lists of) values. Next to being a recipe for BePorter, it may also give specific information on how to build a particular application on BeOS (see below).
+A .bep file is a ''recipe'' that haikuporter uses to fetch, patch, build and install a software package. It is an ASCII file that contains a list of keys with corresponding (lists of) values. Next to being a recipe for haikuporter, it may also give specific information on how to build a particular application on BeOS (see below).
 
 == Syntax ==
@@ -61 +61 @@
  * the line of the key label ends with an opening brace '{', with nothing following it (except for whitespace)
  * each line is indented by whitespace (tabs or spaces)
- * the closing brace '}' is on on a seperate line, preceded by whitespace
+ * the closing brace '}' is on on a separate line, preceded by whitespace
  * the lines between the braces are interpreted as a shell script (bash); hence, it is possible to use conditional execution and insert comments using '#' (see below)
 
 === List of keys ===
 
-The following keys are currently supported in BePorter:
+The following keys are currently supported in haikuporter:
 
 ||Key||Description||Type||Syntax||Mandatory||Default||
@@ -72 +72 @@
 ||{{{HOMEPAGE}}}||URI pointing to the official homepage of the software package||single||URI||yes||-||
 ||{{{SRC_URI}}}||(a list of) URI(s) pointing to the source code archive of the software package||single, list||URI||yes||-||
-||{{{REVISION}}}||indicates the BePort revision||single||integer ({{{1}}}, {{{2}}}, {{{3}}}, ...)||yes||-||
-||{{{STATUS_R5}}}||indicates the status of this port on BeOS R5||single||status ({{{untested}}}, {{{unstable}}}, {{{stable}}})||no||{{{untested}}}||
-||{{{STATUS_BONE}}}||indicates the status of this port on BeOS BONE/Dano and Zeta||single||status ({{{untested}}}, {{{unstable}}}, {{{stable}}})||no||{{{untested}}}||
+||{{{REVISION}}}||indicates the HaikuPort revision||single||integer ({{{1}}}, {{{2}}}, {{{3}}}, ...)||yes||-||
 ||{{{STATUS_HAIKU}}}||indicates the status of this port on Haiku||single||status ({{{untested}}}, {{{unstable}}}, {{{stable}}})||no||{{{untested}}}||
-||{{{DEPEND}}}||(list of) !BePort(s) this port depends upon||single, list||{{{category/portname >= portversion}}}||no||-||
+||{{{DEPEND}}}||(list of) !HaikuPort(s) this port depends upon||single, list||{{{category/portname >= portversion}}}||no||-||
 ||{{{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||-||
+||{{{DISTRO}}}||list of shell commands to execute in order to install to a DESTDIR||shell||shell commands||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}}}. BePorter detects which BeOS platform it is running on and set the {{{BEPORTS_PLATFORM}}} variable accordingly.
+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.
 
 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.
@@ -96 +95 @@
 }}}
 
-When a key is not listed in the BepFile, BePorter assumes the default value, or an empty string/list (when no default value is specified above).
+When a key is not listed in the BepFile, haikuporter assumes the default value, or an empty string/list (when no default value is specified above).
 
-Note: It is possible that the names and/or the use of these keys may change as BePorter evolves. Keys may also be added and removed. When BePorter gets a release, the key set shall be frozen.
+Note: It is possible that the names and/or the use of these keys may change as haikuporter evolves. Keys may also be added and removed. When haikuporter gets a release, the key set shall be frozen.