| 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''': |
| | 1 | == Introduction == |
| | 2 | |
| | 3 | 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. |
| | 4 | |
| | 5 | == Syntax == |
| | 6 | |
| | 7 | === Key types === |
| | 8 | |
| | 9 | There are three types of keys in a !BepFile: single-value, list-of-values and shell-commands. |
| | 10 | |
| | 11 | The key label is subject to the following rules: |
| | 12 | * the key label must be in all capitals and consist only of letters (A-Z) and underscores |
| | 13 | * there may be no whitespace in front of the key label |
| | 14 | * there may be whitespace around the '=', but it is not required |
| | 15 | |
| | 16 | ==== A key with a '''single value''' ==== |
| 28 | | The following keys are to be currently supported in BePorter: |
| | 40 | |
| | 41 | ==== A key with a '''list of shell commands''' ==== |
| | 42 | |
| | 43 | {{{ |
| | 44 | KEY = { |
| | 45 | command1 |
| | 46 | command2 |
| | 47 | command3 |
| | 48 | } |
| | 49 | }}} |
| | 50 | |
| | 51 | The syntax is subject to these rules: |
| | 52 | * the line of the key label end with an opening brace '{', with no command following it |
| | 53 | * one command is entered per line |
| | 54 | * every command is indented by whitespace (tabs or spaces) |
| | 55 | * the closing brace '}' is on on a seperate line, preceded by whitespace |
| | 56 | |
| | 57 | === List of keys === |
| | 58 | |
| | 59 | The following keys are currently supported in BePorter: |