From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: dash.el [was: Re: Imports / inclusion of s.el into Emacs] Date: Tue, 12 May 2020 15:50:52 -0400 Message-ID: References: <35DBF02E-44D7-41E5-A217-7D6EC84ED221@icloud.com> <83d07984ux.fsf@gnu.org> <83tv0l6kgd.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="25854"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: rms@gnu.org, joostkremers@fastmail.fm, Emacs-devel@gnu.org, ams@gnu.org, pcr910303@icloud.com, phillip.lord@russet.org.uk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 12 21:51:56 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 1jYawW-0006bm-7I for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 21:51:56 +0200 Original-Received: from localhost ([::1]:60886 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYawV-0007lS-7F for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 15:51:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49948) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYavc-0006N2-4W for Emacs-devel@gnu.org; Tue, 12 May 2020 15:51:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:43829) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYava-0003ut-Ex; Tue, 12 May 2020 15:50:59 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2DCAF450C40; Tue, 12 May 2020 15:50:56 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 87D8D450BBD; Tue, 12 May 2020 15:50:54 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1589313054; bh=o0PpEjKi/DJmQ+eXwwDx8bWJzMu8Jlo92pmfxibblxQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=l4m7nR5HadMxw29j3RVFAsXTOTBM59o3ZzMw/3wr2yJSFLHPdjLunrEJu5qrkiOKd oQ09FGGSNGo62fvD+AhAI0cNmIfbTH0IdbJ4RguylzPCkZGKYU1xd1Nq1cVuZfqA8o aCH70QM/AJXLtsRofmkHL/luRJsuRzN517DmN7BzSL8q4PQ452xdnGq/dZgoNXrja0 aZgedDEIu+kV3ZjKe/gRwRG+GQjATplkQs7oGNHEFE9S5pV8qSxTav4hvL98L1JoOe 55OvvnCfK1uR3p58+P+6wjyhgf3gPuF9gBSHC/t0qVOCluObbNfF8CwiUsDuyZdrs1 Ss7lvXrhcXIMQ== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 34ACC120CD7; Tue, 12 May 2020 15:50:54 -0400 (EDT) In-Reply-To: <83tv0l6kgd.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 12 May 2020 22:07:30 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/12 13:54:09 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:250036 Archived-At: > 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? Being a GNU ELPA package does not mean "intends to be brought into core". Never has, never will. There are packages in GNU ELPA which I'd like to see included in Emacs's tarball (either by moving them to emacs.git or by bundling them when creating the tarball). Currently, these are just plans, tho. > If not, can we come up with such a mechanism? I guess we could. We'd first have to clarify exactly how this mechanism would be used in order to know how to design it. But at least we could start by just adding a special header `On-The-Way-To-Emacs: yes` for those packages which we "intend" to include in the tarball. > A package that is thus declared can then be exempt from some of the > requirements (we still need to agree on which ones, though). If we only label those rare ones for which we do have plans to integrate them, we don't need to "agree first" since in case of disagreement the package just won't be integrated. Personally I don't see much benefit in such labeling: the way I expect it to work is rather: - Shouldn't we include SuperFoo into the tarball? - Oh, yes, good idea. Let's see ... is it in a good enough shape? - Almost, we just have to fix this and that. - OK, let's do that. - [time passes] - Alright, now this and that has been fixed, let's include it. - Great, thanks, done. No labeling involved. Stefan