From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alexandre Garreau Newsgroups: gmane.emacs.devel Subject: Re: Contradictiory directions Date: Wed, 15 Dec 2021 16:11:11 +0100 Message-ID: <4228873.32GBL0O4vs@galex-713.eu> References: <20211211035614.15517.53830@vcs0.savannah.gnu.org> <877dc6tjz0.fsf_-_@yahoo.com> <871r2e5g4u.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39314"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?ISO-8859-1?Q?=D3scar?= Fuentes To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 15 16:28:50 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mxWD3-000A15-70 for ged-emacs-devel@m.gmane-mx.org; Wed, 15 Dec 2021 16:28:49 +0100 Original-Received: from localhost ([::1]:54672 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mxWD2-0004bD-8Q for ged-emacs-devel@m.gmane-mx.org; Wed, 15 Dec 2021 10:28:48 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:35424) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxVwD-0006cn-Jt for emacs-devel@gnu.org; Wed, 15 Dec 2021 10:11:25 -0500 Original-Received: from [2a00:5884:8305::1] (port=36506 helo=galex-713.eu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mxVw4-0007U8-J5 for emacs-devel@gnu.org; Wed, 15 Dec 2021 10:11:25 -0500 Original-Received: from gal by galex-713.eu with local (Exim 4.94.2) (envelope-from ) id 1mxVvz-0039Qi-W2; Wed, 15 Dec 2021 16:11:12 +0100 In-Reply-To: <871r2e5g4u.fsf@telefonica.net> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:5884:8305::1 (failed) Received-SPF: pass client-ip=2a00:5884:8305::1; envelope-from=galex-713@galex-713.eu; helo=galex-713.eu X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:282057 Archived-At: Le merkredo, 15-a de decembro 2021, 11-a horo kaj 14:41 CET =C3=93scar Fuen= tes=20 a =C3=A9crit : > Po Lu writes: >=20 >=20 >=20 > > It's still based on looking at the names of modules: proprietary > > modules could easily be renamed so that their filenames are the same > > as the free ones, and vice versa: it is not concrete at all. >=20 > Propietary modules can define any symbol, so the > "this_module_is_fine_with_gnus" or whatever trick is used on Emacs and > gcc modules is even less of a solution. I can foresee a propietary > module playing that trick, but changing the name of the module and > creating a name collision with some of the most popular modules out > there is a bit too risky even for the most adventurous propietary > vendor. except a symbol with written =E2=80=9Cgpl-compatible=E2=80=9D on it might b= e legally akin=20 to =E2=80=9CI accept my module can be relicensed to GPLv3=E2=80=9D, which m= ay be akin to a=20 license. From there, we could feel allowed to distribute the library and=20 modified versions of it at will, so that would =E2=80=9Csuffice=E2=80=9D to= make it free- software. > > The PCRE and csvtable modules are also in the public domain. > > Proprietary versions of them could be created ino the future. >=20 > So you just decidead that all those versions that allow to distribute > non-free versions of the code are incompatible with the GPL after all? > No, but enough for them to *potentially become* so *without being noticed*= =20 by emacs or even the users themselves=E2=80=A6 =E2=80=A6what if one day mac os x or ubuntu or windows starts bundling a ve= rsion=20 of sqlite with special =E2=80=9Cimproved=E2=80=9D extensions that are made = proprietary? we=20 don=E2=80=99t want that. We want emacs to break in that case, and potentia= lly the=20 users to do something to become themselves responsible of a such=20 combination of software. > > BTW, the term "allowlist" is confusing. It took me a while to guess > > its meaning. Why not use the industry-standard term "whitelist" > > instead? > Today you are in the mood of picking an argument, aren't you? ;-) The more we feel in an adversarial mood, the more we should attempt to=20 adopt a kind and benevolent mindset. That=E2=80=99s best for everybody, fo= r=20 emacs, and even four each one=E2=80=99s own arguments.