Hello > I am working with the NixOS Linux Distribution [nixos], which has a > fairly radical approach to package management. If you aren't familiar > with it, essentially all packages are installed in isolation - such that > packages cannot interfere with each other.
good. > This is causing a bit of a problem with PostgreSQL extensions that are > usually installed via CREATE EXTENSION. For extensions to be used, a > .control file must be placed in SHAREDIR/extension, but this is not > possible under NixOS as once PostgreSQL is installed that directory is > essentially immutable. What about shared objects, .sql files and documentation an extension may have to install ? > What wolud work best for us is to allow this path to be configurable, > ideally through either an environment variable, command line switch, or > (and this is the least desirable) a postgresql.conf option. There is another point into allowing installation in different path : "make check" and "make installcheck" targets... > Would love to hear your thoughts. Once I get confirmation on the best > approach to take, I can try my hand at providing a patch. No idea on the best approach yet. But I am interested in this topic (for debian packaging). PS: I have a serie of bugfix and patches pending in the current commitfest (http://commitfest.postgresql.org) to help build with VPATH. You may be interested in them... -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation
signature.asc
Description: This is a digitally signed message part.
