Summary: | dev-db/postgresql-server: put *.conf files into /etc/postgresql-${SLOT} directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marc Schiffbauer <mschiff> |
Component: | Current packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | john, titanofold |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marc Schiffbauer
2011-02-04 13:44:57 UTC
This can be resolved. It cannot be resolved in one commit. It will take some time for the fix to really come about. A symlink will not be used as the solution. Adding some info to the discussion, see also bug 175195 from 2007. Placing configuration files in /var/lib breaks the FHS[1]. People putting /etc under version control are unable to track config changes. People creating backups of /etc to secure host configuration are doomed. Upstream[2] supports moving config files out of the data storage. This can be done with runtime configuration, or alternatively, as Marc suggested, using symlinks. Thanks. [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLIBVARIABLESTATEINFORMATION "Users must never need to modify files in /var/lib to configure a package's operation." [2] http://www.postgresql.org/docs/9.0/interactive/runtime-config-file-locations.html "If you wish to keep the configuration files elsewhere than the data directory, the postgres -D command-line option or PGDATA environment variable must point to the directory containing the configuration files, and the data_directory parameter must be set in postgresql.conf (or on the command line) to show where the data directory is actually located. Notice that data_directory overrides -D and PGDATA for the location of the data directory, but not for the location of the configuration files." |