| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Subject: | Re: extension_control_path |
| Date: | 2014-02-06 14:51:47 |
| Message-ID: | CAM-w4HPorv3rU8B+iOJ_F0AMOn0oV_NH45RG+7YHJFMdEiehbQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 4, 2014 at 6:07 PM, David E. Wheeler <david(at)justatheory(dot)com> wrote:
> The install failed, of course, because extensions want to install in $PGROOT/share/extensions.
Homebrew sounds kind of confused. Having a non-root user have access
to make global system changes sounds like privilege escalation
vulnerability by design.
However putting that aside, it is fairly standard for software to
provide two directories for extensions/modules/plugins/etc. One for
distribution-built software such as /usr/share/emacs/site-lisp/ and
another for sysadmin customizations such as
/usr/local/share/emacs/site-lisp. The same idea as /usr/share/perl and
/usr/local/share/perl or with Python or anything else.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-06 15:04:54 | Re: updated emacs configuration |
| Previous Message | Alvaro Herrera | 2014-02-06 14:50:34 | Re: updated emacs configuration |