pgsql: Automate the maintenance of SO_MINOR_VERSION for our shared libr
| От | Tom Lane |
|---|---|
| Тема | pgsql: Automate the maintenance of SO_MINOR_VERSION for our shared libr |
| Дата | |
| Msg-id | E1bZidm-0005H6-33@gemulon.postgresql.org обсуждение исходный текст |
| Список | pgsql-committers |
Automate the maintenance of SO_MINOR_VERSION for our shared libraries. Up to now we've manually adjusted these numbers in several different Makefiles at the start of each development cycle. While that's not much work, it's easily forgotten, so let's get rid of it by setting the SO_MINOR_VERSION values directly from $(MAJORVERSION). In the case of libpq, this dev cycle's value of SO_MINOR_VERSION happens to be "10" anyway, so this switch is transparent. For ecpg's shared libraries, this will result in skipping one or two minor version numbers between v9.6 and v10, which seems like no big problem; and it was a bit inconsistent that they didn't have equal minor version numbers anyway. Discussion: <21969.1471287988@sss.pgh.pa.us> Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/a3bce17ef1ca6408e8d1e7b10fb767aef1729be6 Modified Files -------------- src/interfaces/ecpg/compatlib/Makefile | 2 +- src/interfaces/ecpg/ecpglib/Makefile | 2 +- src/interfaces/ecpg/pgtypeslib/Makefile | 2 +- src/interfaces/libpq/Makefile | 2 +- src/tools/RELEASE_CHANGES | 30 ++++++++++++++++-------------- 5 files changed, 20 insertions(+), 18 deletions(-)
В списке pgsql-committers по дате отправления: