Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mL4Ir-0005TI-JQ for pgsql-bugs@arkaria.postgresql.org; Tue, 31 Aug 2021 13:59:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mL4Iq-0008GH-JN for pgsql-bugs@arkaria.postgresql.org; Tue, 31 Aug 2021 13:59:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mL4Fq-0004Jg-Fh for pgsql-bugs@lists.postgresql.org; Tue, 31 Aug 2021 13:56:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mL4Fl-0003MR-BI for pgsql-bugs@lists.postgresql.org; Tue, 31 Aug 2021 13:56:45 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 17VDuHdl1601241; Tue, 31 Aug 2021 09:56:17 -0400 From: Tom Lane To: bchen90@163.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17169: Does PG involve GPL license? In-reply-to: <17169-8afad91d69a6dfd9@postgresql.org> References: <17169-8afad91d69a6dfd9@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 31 Aug 2021 03:32:51 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1601239.1630418177.1@sss.pgh.pa.us> Date: Tue, 31 Aug 2021 09:56:17 -0400 Message-ID: <1601240.1630418177@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Recently, We planned to use PostgreSQL for owner project, so we > retrieved the license of all PG source code. And the following files which > involve the GPL and perl copyright license. > config > ax_pthread.m4 > check_decls.m4 > config.guess > config.sub > libtool.m4 > pkg.m4 Those files come from autoconf (they are part of the source code that goes into the configure script). The autoconf manual says, in its FAQ section: 20.1 Distributing `configure' Scripts ===================================== What are the restrictions on distributing `configure' scripts that Autoconf generates? How does that affect my programs that use them? There are no restrictions on how the configuration scripts that Autoconf produces may be distributed or used. In Autoconf version 1, they were covered by the GNU General Public License. We still encourage software authors to distribute their work under terms like those of the GPL, but doing so is not required to use Autoconf. Of the other files that might be used with `configure', `config.h.in' is under whatever copyright you use for your `configure.ac'. `config.sub' and `config.guess' have an exception to the GPL when they are used with an Autoconf-generated `configure' script, which permits you to distribute them under the same terms as the rest of your package. `install-sh' is from the X Consortium and is not copyrighted. regards, tom lane