Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1a2CIo-0002lo-UA for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Nov 2015 06:14:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1a2CIo-0008V6-2m for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Nov 2015 06:14:38 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1a2CIm-0008Ux-6v for pgsql-hackers@postgresql.org; Fri, 27 Nov 2015 06:14:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1a2CIf-00009C-Gy for pgsql-hackers@postgresql.org; Fri, 27 Nov 2015 06:14:35 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id tAR6EIuI029414; Fri, 27 Nov 2015 01:14:19 -0500 From: Tom Lane To: Craig Ringer cc: Euler Taveira , YUriy Zhuravlev , PostgreSQL Hackers , =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= Subject: Re: WIP: About CMake v2 In-reply-to: References: <4184974.kkvGJ5GoEX@dinodell> <3993879.VcJEeiShpZ@dinodell> <20151126164216.GA2521@awork2.anarazel.de> <2680925.vIMPA4fzVa@dinodell> <5657877F.3080200@timbira.com.br> <26039.1448599175@sss.pgh.pa.us> Comments: In-reply-to Craig Ringer message dated "Fri, 27 Nov 2015 13:50:20 +0800" Date: Fri, 27 Nov 2015 01:14:18 -0500 Message-ID: <29413.1448604858@sss.pgh.pa.us> X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Craig Ringer writes: > One thing to consider: I can't imagine backporting this to all supported > back branches, it'd be a switch for the next release. Right? Agreed. > That means he doesn't have to worry about what RH / Debian policy for their > old versions is. RH isn't going to release PostgreSQL 9.7 or whatever for > RHEL6, Debian isn't going to release it for Wheezy, etc. Well, they won't if we make it impossible for them to do so. More generally, I do not buy this argument for one second as a reason why we can demand latest-and-greatest cmake, rather than something that's likely to be readily available on a wide variety of platforms. Devrim is not the only person in the world who will be needing to build PG on RHEL6, or even older platforms. If you take a close look at our build requirements, you will notice a general distaste for insisting on latest anything. cmake is not going to escape that project bias. Do you really think a project that still works with C89, Perl 5.8.something, Python 2.3, bison 1.875, yadda yadda is readily going to accept a patch that requires this year's cmake? It would take a fairly impressive technical argument why working with older cmakes is impossible/impractical before that will happen. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers