| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extensions Dependency Checking |
| Date: | 2011-04-05 22:50:54 |
| Message-ID: | A1333232-F31E-4890-AE91-602D7EDD1254@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Apr 5, 2011, at 1:59 PM, Aidan Van Dyk wrote:
> Versions are useful for figuring out if I should upgrade packages or
> not. But I believe the extension framework has explicitly made the
> "upgrade" problem a manual one at this point, either taking
> destination versions from the control, or the alter command.
>
> So for PGXN's problem, I see the point of versions being required.
Okay, thanks, I'm convinced (and relieved; I hated to be bringing something like this up so close to launch).
> But for installation the dependancy graph, "provides/features" rather
> than versions are much more useful. And automatic feature/provides
> (like library so, and symbol versions in the OS package world,
> "objects" in PG world) would definitely be nice, but my Makefile can
> build those for me for now until 9.2 (or 9.3, 9.3, etc), if only I had
> a way to track them with my installed extension ;-) </stop begging>
I'm sure a patch would be welcomed. ;-P
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2011-04-05 22:52:21 | Re: .ini support for .pgpass |
| Previous Message | Joshua D. Drake | 2011-04-05 22:43:29 | Re: .ini support for .pgpass |