| From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Yeb Havinga <yebhavinga(at)gmail(dot)com> |
| Subject: | Re: Satisfy extension dependency by one of multiple extensions |
| Date: | 2011-09-24 21:01:00 |
| Message-ID: | 1059002111.45820.1316898060450.JavaMail.root@mail-1.01.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
All,
> >> We might want to have a system where an extension can declare that
> >> it
> >> "provides" capabilites, and then have another extension "require"
> >> those
> >> capabilities. That would be a neater solution to the case that
> >> there are
> >> multiple extensions that all provide the same capability.
>
> +1
As a warning, this is the sort of thing which DEB and RPM have spent years implementing ... and still have problems with. Not that we shouldn't do it, but we should be prepared for the amount of troubleshooting involved, which will be considerable.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2011-09-24 21:18:19 | Re: psql setenv command |
| Previous Message | Marti Raudsepp | 2011-09-24 19:57:41 | Re: [PATCH] Log crashed backend's query (activity string) |