From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq.rc make rule |
Date: | 2008-02-25 21:36:24 |
Message-ID: | 937d27e10802251336p53684591s21c0cafb55b236cb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 25, 2008 at 7:21 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> The libpq.rc make rule says:
>
> # depend on Makefile.global to force rebuild on re-run of configure
> $(srcdir)/libpq.rc: libpq.rc.in $(top_builddir)/src/Makefile.global
> sed -e 's/\(VERSION.*\),0 *$$/\1,'`date '+%y%j' | sed 's/^0*//'`'/' < $< > $@
>
> However, libpq.rc is also included in the distribution, so whenever a
> distribution is built, the distributed file would be overwritten, which is
> not a nice thing to do.
>
> Could someone explain what the requirement behind this is? The '+%y%j'
> changes every day. Why is libpq the only subsystem that needs a daily
> version number?
It's used on Windows to ensure that installers can do the right thing
when replacing a copy of libpq.dll. The daily build number was the
most maintenance-free way of getting a fourth value for the version
resource.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-02-25 22:03:35 | Re: libpq.rc make rule |
Previous Message | Joshua D. Drake | 2008-02-25 20:28:22 | Re: 8.3 / 8.2.6 restore comparison |