Details | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 2 | magnus | 1 | Running pmksetup |
| 2 | ================ |
||
| 3 | |||
| 4 | For pmk to work and configure software builds correctly, pmksetup must |
||
| 5 | be run (as root) to construct /etc/pmk/pmk.conf, which pmk uses to |
||
| 6 | find most system information instead of detecting it each time. |
||
| 7 | pmksetup is run automatically whenever pmk is installed or |
||
| 8 | upgraded. You should accept any changes presented to you, especially |
||
| 9 | if you are upgrading from an old version (before 0.8.1-3+s5, to be |
||
| 10 | exact). The configuration is maintained with ucf, which should make it |
||
| 11 | easier to merge |
||
| 12 | |||
| 13 | pmksetup needs to be run again whenever a tool that pmksetup needs to |
||
| 14 | detect is installed. To get certain Debian-specific defaults right, |
||
| 15 | this should be done by running `dpkg-reconfigure pmk'. This is a bit |
||
| 16 | of a bug, but it can be worked around by providing an override file |
||
| 17 | (see pmk(1)) with any Debian package using pmk, or by overriding |
||
| 18 | variables when calling make. |