Hello!
RoundCube places its config files within its directory hierarchy. This
is a fine default, but for packages it's important to be able to
override the default. Why? Many sysadmins (and packagers, and package
systems) expect all binaries and data installed under the root of the
package tree to be read-only once they've been installed; think NFS
sharing, or package tools throwing warnings on delete/update when
files don't match the checksums recorded when they were installed.
Config files aren't read-only, and therefore it's important to be able
to place them elsewhere if desired (/etc, for instance.) I've patched
roundcubemail-0.1.1-dep's main.inc:rcmail_load_config() to inspect the
environment and prefix $RCMAIL_CONFIG_DIR if set, rather than
"config", when reading the config files. The default behavior remains
unchanged, of course!
http://netbsd.schmonz.com/patches/roundcube-config-dir.diff
To take advantage of the patch, I added "SetEnv RCMAIL_CONFIG_DIR /etc/
roundcube" to the RoundCube section of my Apache config, and placed
{db,main}.inc.php in /etc/roundcube where I like them. :-)
Sorry this is against an old version, but there's nothing at all
clever about the changes so they should be straightforward to bring up
to date. The installer would need similar help as well.
- Amitai
List info: http://lists.roundcube.net/dev/