Re: [HACKERS] WIP: About CMake v2

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] WIP: About CMake v2
Дата
Msg-id e7945b31-0e69-9d49-7c72-522bd08fb3c4@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] WIP: About CMake v2  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] WIP: About CMake v2  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] WIP: About CMake v2  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] WIP: About CMake v2  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On 1/24/17 8:37 AM, Tom Lane wrote:
> Craig Ringer <craig.ringer@2ndquadrant.com> writes:
>> Personally I think we should aim to have this in as a non default build
>> mode in pg10 if it can be made ready, and aim to make it default in pg11 at
>> least for Windows.
> 
> AFAIK we haven't committed to accepting this at all, let alone trying
> to do so on a tight schedule.  And I believe there was general agreement
> that we would not accept it as something to maintain in parallel with
> the existing makefiles.  If we have to maintain two build systems, we
> have that already.

My preferred scenario would be to replace the Windows build system by
this first, then refine it, then get rid of Autoconf.

The ideal timeline would be to have a ready patch to commit early in a
development cycle, then get rid of the Windows build system by the end
of it.  Naturally, this would need buy-in from Windows developers.

I don't foresee replacing the Autoconf build system by this immediately.

Right now, however, the patch isn't moving at all, and I don't see it
going into PG10, so I'm fine with returning with feedback.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] pg_ls_dir & friends still have a hard-coded superuser check