| | 1 | 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. The syntax is as follows. For a key with a '''single value''': |
| | 2 | |
| | 3 | {{{ |
| | 4 | KEY = "value" |
| | 5 | }}} |
| | 6 | |
| | 7 | The syntax is subject to the following rules: |
| | 8 | * the key label must be in all capitals and consist only of letters (A-Z) and underscores |
| | 9 | * there may be no whitespace in front of the key label |
| | 10 | * there may be whitespace around the '=', but it is not required |
| | 11 | * the value should be enclosed within double quotes |
| | 12 | * there may be whitespace after the closing quote |
| | 13 | |
| | 14 | For a key with a '''list of values''': |
| | 15 | |
| | 16 | {{{ |
| | 17 | KEY = "value1 |
| | 18 | value2 |
| | 19 | value3" |
| | 20 | }}} |
| | 21 | |
| | 22 | The syntax is subject to the rules listed above, plus the following: |
| | 23 | * one value is entered per line, with the first on the line of the key label |
| | 24 | * every value but the first is indented by whitespace (tabs or spaces) |
| | 25 | * only one set of double quotes encloses the list, as is visible from the example above |
| | 26 | * the closing double quote is on the same ling as the last value of the list |
| | 27 | |
| | 28 | The following keys are to be currently supported in BePorter: |
| | 29 | |
| | 30 | {{{DESCRIPTION}}}: |
| | 31 | a (short) description of the software package |
| | 32 | {{{HOMEPAGE}}}: |
| | 33 | URI pointing to the official homepage of the software package |
| | 34 | {{{SRC_URI}}}: |
| | 35 | (a list of) URI(s) pointing to the source code archive of the software package |
| | 36 | {{{UNPACK}}}: |
| | 37 | indicates the type of archive: {{{tgz}}} (tar gzip) or {{{tbz}}} (tar bzip2) |
| | 38 | {{{REVISION}}}: |
| | 39 | indicates the BePort revision: {{{1}}}, {{{2}}}, {{{3}}}, ... |
| | 40 | {{{PATCH}}}: |
| | 41 | indicates whether BeOS-specific patching is required: {{{YES}}} or {{{NO}}} |
| | 42 | default = {{{NO}}} |
| | 43 | {{{WORKING}}}: |
| | 44 | indicates whether this BePort is fully working: {{{YES}}} or {{{NO}}} |
| | 45 | default = {{{YES}}} |
| | 46 | {{{DEPEND}}}: |
| | 47 | list of !BePorts this port depends upon: {{{category/portname >= portversion}}} |
| | 48 | {{{BUILD}}}: |
| | 49 | list of shell commands to execute in order to build the port |
| | 50 | {{{INSTALL}}}: |
| | 51 | list of shell commands to execute in order to install the port |
| | 52 | |
| | 53 | When a key is not listed in the BepFile, BePorter assumes the default value, or an empty string/list (if no default value is specified above). |
| | 54 | |
| | 55 | |
| | 56 | 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. |
| | 57 | |
| | 58 | It is possible to insert '''comments''' in the BepFile. |
| | 59 | * the comment should be preceded with a hash (#) |
| | 60 | * there may be whitespace preceding the '#' |