| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.3 beta breaks some extensions "make install" |
| Date: | 2013-05-14 12:00:56 |
| Message-ID: | 51922778.4050107@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/14/13 7:50 AM, Dimitri Fontaine wrote:
> Marti Raudsepp <marti(at)juffo(dot)org> writes:
>> > all: sql/$(EXTENSION)--$(EXTVERSION).sql
>> >
>> > sql/$(EXTENSION)--$(EXTVERSION).sql: sql/$(EXTENSION).sql
>> > cp $< $@
> That's a recipe for problems. Each time I meet with such a construct in
> an extension's Makefile I propose an hard coded alternative. We're
> speaking of maintaining less than half a dozen file names here, with one
> or two additions per year, in most cases.
I don't think this in particular is a problem. I use something like
that myself. But you should list all the older extension upgrade files
explicitly (to which your point applies).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stas Kelvich | 2013-05-14 12:30:21 | Re: Cube extension improvement, GSoC |
| Previous Message | Peter Eisentraut | 2013-05-14 11:59:23 | Re: PostgreSQL 9.3 beta breaks some extensions "make install" |