|
Lines 1-15
Link Here
|
| 1 |
[ |
1 |
[ |
| 2 |
{ type: install |
2 |
{ type: install |
| 3 |
message: <<EOM |
3 |
message: <<EOM |
| 4 |
Sample configuration files have been installed in "%%ETCDIR%%/" |
4 |
MAME follows an interesting User Experience (UX) design pattern that is aimed |
| 5 |
The configuration data can be copied to your "~/.mame" directory; alternatively, |
5 |
for developers of MAME, as result of this, the expectation on file |
| 6 |
to create clean copies of MAME's configuration, run "mame -createconfig", |
6 |
configuration management might appear counter-intuitive to Users of MAME. If |
| 7 |
the output from this can be stored in ~/.mame or elsewhere. |
7 |
MAME does not find configuration files, it expects to be able to read and write |
|
|
8 |
configuration data to the current working directory, this is counter to |
| 9 |
what users expect on their systems. |
| 8 |
|
10 |
|
| 9 |
To run mame with a custom path, run "mame -inipath path-to-mame.ini" |
11 |
Sample configuration files have been installed in: |
|
|
12 |
"%%ETCDIR%%/" |
| 13 |
The samples can be copied to your "~/.mame" directory to avoid having MAME |
| 14 |
write configuration data elsewhere. |
| 10 |
|
15 |
|
| 11 |
By default, MAME will search and write to the current working directory, unless |
16 |
To create clean copies of MAME's configuration files, execute: |
| 12 |
it finds configuration data. |
17 |
"mame -createconfig" |
|
|
18 |
the output from this can be stored in ~/.mame or a custom path. |
| 19 |
|
| 20 |
To run MAME with custom configuration path(s), execute: |
| 21 |
"mame -inipath /var/db/mame /usr/local/etc/mame" |
| 22 |
|
| 23 |
See mame(6) for more information. |
| 13 |
EOM |
24 |
EOM |
| 14 |
} |
25 |
} |
| 15 |
] |
26 |
] |