From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: dash.el [was: Re: Imports / inclusion of s.el into Emacs] Date: Tue, 12 May 2020 22:07:30 +0300 Message-ID: <83tv0l6kgd.fsf@gnu.org> References: <35DBF02E-44D7-41E5-A217-7D6EC84ED221@icloud.com> <83d07984ux.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="92586"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, joostkremers@fastmail.fm, Emacs-devel@gnu.org, ams@gnu.org, pcr910303@icloud.com, phillip.lord@russet.org.uk To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 12 21:08:57 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 1jYaGu-000NsP-3i for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 21:08:56 +0200 Original-Received: from localhost ([::1]:49010 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYaGt-0004Uq-72 for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 15:08:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44610) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYaG5-0003rJ-4D for Emacs-devel@gnu.org; Tue, 12 May 2020 15:08:05 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:48215) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYaG3-0005RM-MJ; Tue, 12 May 2020 15:08:03 -0400 Original-Received: from [176.228.60.248] (port=3348 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYaFr-0002hX-Oe; Tue, 12 May 2020 15:07:52 -0400 In-Reply-To: (message from Stefan Monnier on Tue, 12 May 2020 14:42:09 -0400) 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:250025 Archived-At: > From: Stefan Monnier > Cc: rms@gnu.org, joostkremers@fastmail.fm, ams@gnu.org, > phillip.lord@russet.org.uk, pcr910303@icloud.com, Emacs-devel@gnu.org > Date: Tue, 12 May 2020 14:42:09 -0400 > > > It won't stay hypothetical if we allow incoherent packages into ELPA > > and start accepting their use in other packages and eventually in core. > > We can simply refuse to incorporate `s.el` into core and then any > package which wants to be in core will first have to sop using `s.el`. > > Accepting `s.el` into GNU ELPA does not mean we will accept it > into core. Emacs and GNU ELP are both under our control, but we don't > need to (and we don't) apply the same rules to the two. Do we have a mechanism to declare that a package is not intended to be brought into core, unless changed to follow the same standards and guidelines as the core does? If not, can we come up with such a mechanism? A package that is thus declared can then be exempt from some of the requirements (we still need to agree on which ones, though). maybe such packages should be in a separate subdirectory of ELPA. Unless that unduly complicates management or package.el.