From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: ELPA policy Date: Mon, 09 Nov 2015 03:25:50 -0600 Message-ID: <86y4e7a5i9.fsf@stephe-leake.org> References: <563ABD66.6070700@yandex.ru> <563AC64E.9060105@yandex.ru> <87twp0d2xp.fsf@md5i.com> <563B5E82.8070003@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447061192 27852 80.91.229.3 (9 Nov 2015 09:26:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 Nov 2015 09:26:32 +0000 (UTC) Cc: mwd@md5i.com, emacs-devel@gnu.org, dgutov@yandex.ru To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 09 10:26:18 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZviiO-0000jW-RY for ged-emacs-devel@m.gmane.org; Mon, 09 Nov 2015 10:26:16 +0100 Original-Received: from localhost ([::1]:51163 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZviiO-0000Lk-2M for ged-emacs-devel@m.gmane.org; Mon, 09 Nov 2015 04:26:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46082) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZviiG-0000GI-C7 for emacs-devel@gnu.org; Mon, 09 Nov 2015 04:26:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZviiD-0004ob-Nm for emacs-devel@gnu.org; Mon, 09 Nov 2015 04:26:08 -0500 Original-Received: from gproxy4-pub.mail.unifiedlayer.com ([69.89.23.142]:41214) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1ZviiD-0004oP-GM for emacs-devel@gnu.org; Mon, 09 Nov 2015 04:26:05 -0500 Original-Received: (qmail 2200 invoked by uid 0); 9 Nov 2015 09:25:59 -0000 Original-Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy4.mail.unifiedlayer.com with SMTP; 9 Nov 2015 09:25:59 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw2 with id fMRs1r00L2UdiVW01MRvKb; Mon, 09 Nov 2015 02:25:57 -0700 X-Authority-Analysis: v=2.1 cv=Jv9i8qIC c=1 sm=1 tr=0 a=CQdxDb2CKd3SRg4I0/XZPQ==:117 a=CQdxDb2CKd3SRg4I0/XZPQ==:17 a=DsvgjBjRAAAA:8 a=f5113yIGAAAA:8 a=9i_RQKNPAAAA:8 a=hEr_IkYJT6EA:10 a=x_XPkuGwIRMA:10 a=qtqOOiqGOCEA:10 a=pGLkceISAAAA:8 a=mDV3o1hIAAAA:8 a=J9aIBkEO5wLS4xx4zfoA:9 Original-Received: from [76.218.37.33] (port=52381 helo=TAKVER2) by host114.hostmonster.com with esmtpa (Exim 4.84) (envelope-from ) id 1Zvii2-0003X4-1q; Mon, 09 Nov 2015 02:25:54 -0700 In-Reply-To: (John Wiegley's message of "Sun, 08 Nov 2015 08:30:17 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (windows-nt) X-Identified-User: {2442:host114.hostmonster.com:stephele:stephe-leake.org} {sentby:smtp auth 76.218.37.33 authed with stephen_leake@stephe-leake.org} X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.89.23.142 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:193695 Archived-At: John Wiegley writes: >>>>>> Richard Stallman writes: > >>> I'd like to know more about this. How does the user access these bundled >>> packages; by installing them with M-x package-install? > >> I think they should appear, to the user, like any other standard part of >> Emacs. > > If that's the case, it changes my thoughts on what needs to be in core, and > what should be in ELPA. Until now I was thinking ELPA required Internet > access; but if there are parts of ELPA that "come in the box", then I'd like > to see more packages there. It depends on what git repository the package is in, and how the ELPA packages are included in core. My impression is that the latest proposal for doing this is to keep "core ELPA" packages in the emacs repository (not the Gnu ELPA repository), and fix the Gnu ELPA server scripts to work with that. Then all core Emacs developers see the core ELPA packages in their current workflow, and they are released along with Emacs. They are also released separately to Gnu ELPA, and they appear in `list-packages' (as other core packages do now); that's what makes them "ELPA core packages" as opposed to "core code". That's an elegant solution. The alternative is to figure out how to merge a partial checkout of the Gnu ELPA repository into an Emacs git checkout without confusing git and make; not at all easy. -- -- Stephe