From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: David Engster Newsgroups: gmane.emacs.devel Subject: Re: ELPA policy Date: Sat, 09 May 2020 09:35:49 +0200 Message-ID: <875zd57e7e.fsf@randomsample> References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> <83zhaij4qn.fsf@gnu.org> <835zd6ihns.fsf@gnu.org> <83h7wphblf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="90972"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) Cc: Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 09 09:36:39 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 1jXK2J-000NXt-75 for ged-emacs-devel@m.gmane-mx.org; Sat, 09 May 2020 09:36:39 +0200 Original-Received: from localhost ([::1]:38918 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jXK2H-0001wU-M7 for ged-emacs-devel@m.gmane-mx.org; Sat, 09 May 2020 03:36:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37386) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jXK1j-0001Wx-JN for emacs-devel@gnu.org; Sat, 09 May 2020 03:36:03 -0400 Original-Received: from zplane.randomsample.de ([2a03:4000:42:1a1:9400:eeff:feb4:c8a0]:56620) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jXK1h-0006WB-MI; Sat, 09 May 2020 03:36:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=randomsample.de; s=a; h=Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=p8E/i2KM+mCebGBqMbQAjC9SSbVK3GBpPGYIqTOmh6M=; b=R6Hw6t9SbbXhJBVX+iGTQGG4F ivcM7V8lEMNeMpBeefyyRS4XgS5YRpQJBksNbiIwp5gdXe9wb+qJQHWjFEFouhSsbiBimGP/OyuF8 s78UYsRBPmMW7JPM809CjhrIJta5s3rtA9hQG27vOTQbr1+Ql0Qa7snbaod+uYZ4mgIr62YsOuDhS ywuV+CijlnmYO04h6AKF5kBac0X+s4UVai/39BwlnOwm7xpcRas99Y7DWWheWyZXt6tBK4qG9gjc9 lw9RUtqH24NZBvDJ0tEf6x8fTuwuEpthItwXey2nixfbj9In5Y516lxJZjVgaNAZmlfT64wR2psR8 y2BGr1wGg==; Original-Received: from [95.90.186.238] (helo=void) by zplane.randomsample.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jXK1c-00016N-0s; Sat, 09 May 2020 09:35:56 +0200 In-Reply-To: <83h7wphblf.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 May 2020 09:22:04 +0300") Received-SPF: pass client-ip=2a03:4000:42:1a1:9400:eeff:feb4:c8a0; envelope-from=deng@randomsample.de; helo=zplane.randomsample.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/09 03:35:57 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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:249363 Archived-At: > And why do I have to submit bug reports against an ELPA package for > violation of our coding conventions? I'd expect the maintainer of the > package to be asked to fix those as a precondition for accepting the > package in GNU ELPA, or at least as a long-term plan to which the > maintainer agreed in advance (in which case no bug report would have > been necessary). > > What am I missing here? The README for GNU ELPA states: We do not impose a particular coding style on GNU ELPA packages, but of course we recommend the coding style used in Emacs's own source code. Furthermore we recommend the following: - Use `cl-lib` rather than `cl` if it all possible. - Use lexical-binding if it all possible. - Try and fix the warnings emitted when compiling the package with a recent Emacs. From: http://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/README So from my understanding: Following Emacs coding guidelines is a recommendation, but not a precondition for getting packages into GNU ELPA. If we start bundling certain ELPA packages with Emacs proper, then of course these special "core packages" would need to adhere to the Emacs coding style. I don't see any difficulty in making this distinction between core packages and the rest. And I also don't see any problem to put s.el in ELPA and say: note that using this package is against the Emacs coding style, so as long as you depend on this packages, it cannot become a "core package" in the future (same for dash.el). -David