From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: non-gnu elpa issue tracking Date: Thu, 10 Dec 2020 19:05:20 +0300 Message-ID: References: <20201209125516.lenqswi7fhiscbr2@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31368"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Emacs-Devel List , Boruch Baum , Thibaut Verron , Stefan Kangas To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 10 18:23:41 2020 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 1knPfJ-00083g-0f for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 18:23:41 +0100 Original-Received: from localhost ([::1]:33500 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knPfH-0006Sy-Pc for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 12:23:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44974) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knPKP-0004bE-Uu for emacs-devel@gnu.org; Thu, 10 Dec 2020 12:02:07 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:55227) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knPKK-0007ky-Ob for emacs-devel@gnu.org; Thu, 10 Dec 2020 12:02:05 -0500 Original-Received: from localhost ([::ffff:41.202.241.31]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E367.000000005FD25466.00003EF8; Thu, 10 Dec 2020 10:01:26 -0700 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:260661 Archived-At: * Stefan Monnier [2020-12-10 18:49]: > > Am I correct to understand that if some developers decide that they do > > not want their package included in non-GNU ELPA, the only way that > > they can enforce this decision is to use a less permissive license for > > future releases? > > Yes and no: the legality of distributing an ELisp package with a license > that is not compatible with GPLv3+ is dubious (because that code > likely can't run without linking to Emacs which is GPLv3+). > > So it's not clear whether they could legally use a less > permissive license. I guess that quoted paragraph is meant to say that when package is in non-GNU ELPA under GNU GPL let us say, and author objects to be included in non-GNU ELPA, which is unlikely, that such author could change license of package. For your quote paragraph, Stefan, I am not sure on that. I know exactly what you mean. And I still do not know the final answer. Emacs Lisp is programming language. Software can be written in Perl, Lua, Forth, CLISP, GCL, Guile and can be proprietary software, people do that. Would then Emacs package be considered extension of Emacs or program in itself, that is what I do not know. Maybe if program uses Emacs interface cannot be proprietary. But if it does not use the interface then maybe it could. Not that I want, but those are doubts.