| | 398 | * Custom install locations |
| | 399 | |
| | 400 | If you wish to install the OpenGuides modules in a private directory, |
| | 401 | you will need to specify this when you run the Build.PL. |
| | 402 | |
| | 403 | If you are using version 0.20 of Module::Build, do: |
| | 404 | |
| | 405 | perl Build.PL install_path=lib=/path/to/my/modules/ \ |
| | 406 | install_path=script=/path/to/my/bin/ \ |
| | 407 | install_path=arch=/path/to/my/modules/auto/ \ |
| | 408 | install_path=libdoc=/path/to/my/man/ \ |
| | 409 | install_path=bindoc=/path/to/my/man/ |
| | 410 | |
| | 411 | Or for earlier versions of Module::Build, do: |
| | 412 | |
| | 413 | perl Build.PL config='sitelib=/path/to/my/modules/' |
| | 414 | |
| | 415 | If any or all of the modules required by the OpenGuides scripts are in |
| | 416 | a private directory, then you'll need to tell the scripts where to find |
| | 417 | them. See the section above about munging in a custom lib path. |
| | 418 | |
| | 419 | ---------------------------------------------------------------------- |
| | 420 | |
| | 421 | Important note for those using SQLite: |
| | 422 | |
| | 423 | The user your CGI is running as must have write access to not only the |
| | 424 | database file itself, but the directory that the file is in, in order |
| | 425 | that it can write a lockfile. If it doesn't have write access to the |
| | 426 | database file, you'll see errors like "Unhandled error: [DBD::SQLite::db |
| | 427 | do failed...". |
| | 428 | |
| | 429 | ---------------------------------------------------------------------- |
