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: use-package.el -> Emacs core Date: Tue, 10 Nov 2015 18:04:36 -0600 Message-ID: <86a8ql765n.fsf@stephe-leake.org> References: <864mgtaf6l.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447200325 20332 80.91.229.3 (11 Nov 2015 00:05:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Nov 2015 00:05:25 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 11 01:05:14 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 1ZwIuX-0005jl-Qf for ged-emacs-devel@m.gmane.org; Wed, 11 Nov 2015 01:05:13 +0100 Original-Received: from localhost ([::1]:36257 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwIuX-0007Zi-HV for ged-emacs-devel@m.gmane.org; Tue, 10 Nov 2015 19:05:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwIuF-0007Zb-L3 for emacs-devel@gnu.org; Tue, 10 Nov 2015 19:04:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwIuB-0006bz-I2 for emacs-devel@gnu.org; Tue, 10 Nov 2015 19:04:55 -0500 Original-Received: from gproxy7-pub.mail.unifiedlayer.com ([70.40.196.235]:35893) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1ZwIuB-0006bt-Ar for emacs-devel@gnu.org; Tue, 10 Nov 2015 19:04:51 -0500 Original-Received: (qmail 26328 invoked by uid 0); 11 Nov 2015 00:04:45 -0000 Original-Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy7.mail.unifiedlayer.com with SMTP; 11 Nov 2015 00:04:45 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw3 with id g74e1r01F2UdiVW0174hPu; Wed, 11 Nov 2015 00:04:42 -0700 X-Authority-Analysis: v=2.1 cv=Caqbutbl 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=EcQzL7lICyFltdBYIZYA:9 Original-Received: from [76.218.37.33] (port=53290 helo=TAKVER2) by host114.hostmonster.com with esmtpa (Exim 4.84) (envelope-from ) id 1ZwIu0-0001ti-Vc for emacs-devel@gnu.org; Tue, 10 Nov 2015 17:04:41 -0700 In-Reply-To: (John Wiegley's message of "Tue, 10 Nov 2015 10:34:02 -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: 70.40.196.235 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:194006 Archived-At: John Wiegley writes: >>>>>> Stephen Leake writes: > >> What is the rationale for moving this to core instead of Gnu ELPA? (My search of list-packages did not find `use-package' the first time, so I did not realize it is already in Gnu ELPA). > Well, it will be maintained by a core developer. :) Not a good reason; I maintain ada-mode in ELPA, because I want an independent release cycle. But I still consider myself a minor Emacs core developer. > It would also be in the Emacs manual, It can provide a .info file, which will be in the user's top level info list. Is that not sufficient? Hmm. It might be that other sections of the Emacs manual want to reference use-package. They can do so, as long as they clearly label it as an ELPA package, so users will know how to find it. For example: If you use the (really cool) ELPA package @elparef{use-package}, then you can do ... I'm not clear exactly what "@elparef" should do, but it seems like a good idea. Perhaps it should add the "ELPA package" text, so it is done consistently. Can it add a clickable link to the package.el description of the package? > and blessed as an official method for declaring complex package > configuration. Ah. So you are asking us to agree that _this_ package is better than other similar packages. That's a reasonable request in general. But given the controversy around CEDET, I think it needs to wait for emacs 25+, so we can establish a process for such requests. > Further, I wouldn't want it changing on users as ELPA updates. > Once a user downloads Emacs X.Y and reads the manual on how to write > such configurations, the information should remain true until Emacs > X.Z. As the package maintainer, that's under your control; if you don't want it to change, don't change it. You are completely free to determine the release schedule for your ELPA package. If you want it synced with Emacs releases, do that. There is a small race condition window at the actual release, but I don't think that's a significant problem. Proper use of Emacs version in the dependency header should handle that. If you want to work on it between releases, use a branch in ELPA git, or a separate repository. On the other hand, that means you can't release bug fixes, either. Nor really cool but backward-compatible enhancements. I'd rather have a package in ELPA, so I don't have to wait for the next Emacs release. -- -- Stephe