From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Integrating package.el Date: Mon, 04 Jan 2010 11:55:04 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87k4vxiwlj.fsf@lifelogs.com> References: <878wclke6j.fsf@lifelogs.com> <87k4w5lbyb.fsf_-_@lifelogs.com> <87zl50jv52.fsf@lifelogs.com> <87d41rn3wt.fsf_-_@hagelb.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262632207 25981 80.91.229.12 (4 Jan 2010 19:10:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2010 19:10:07 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 20:10:00 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NRsJT-0002TD-AF for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2010 20:09:59 +0100 Original-Received: from localhost ([127.0.0.1]:57804 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRsJT-0007cg-Gf for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2010 14:09:59 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRsHe-0006Cq-PO for emacs-devel@gnu.org; Mon, 04 Jan 2010 14:08:06 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRsHZ-000669-NE for emacs-devel@gnu.org; Mon, 04 Jan 2010 14:08:06 -0500 Original-Received: from [199.232.76.173] (port=43190 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRsHZ-00065b-I1 for emacs-devel@gnu.org; Mon, 04 Jan 2010 14:08:01 -0500 Original-Received: from mx20.gnu.org ([199.232.41.8]:53936) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NRsHV-0002en-5B for emacs-devel@gnu.org; Mon, 04 Jan 2010 14:07:57 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NRr9N-0006HD-BE for emacs-devel@gnu.org; Mon, 04 Jan 2010 12:55:29 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NRr9K-00063B-Li for emacs-devel@gnu.org; Mon, 04 Jan 2010 18:55:26 +0100 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Jan 2010 18:55:26 +0100 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 04 Jan 2010 18:55:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 47 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.90 (gnu/linux) Cancel-Lock: sha1:aFpXFoa+valPBY+ZSPPx3srRa0U= X-detected-operating-system: by mx20.gnu.org: GNU/Linux 2.6 (newer, 3) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:119394 Archived-At: On Sat, 02 Jan 2010 21:38:58 -0800 Phil Hagelberg wrote: PH> I've actually been thinking in even more incremental steps. Installing PH> package.el in Emacs without altering any of the existing Emacs code PH> would be an easy first step and would give some immediate benefit in PH> terms of packages that are not included in Emacs. Agreed. I think it's mature enough and would benefit from the wider exposure. But at that point I think it becomes important to separate the repository into "Emacs supported," "Emacs unsupported," "ELPA," and any others deemed necessary. Then the Emacs-related repositories can be managed by Emacs maintainers and developers and hosted within the Emacs repo while ELPA can remain independent. Can package.el support that? It looks to me, from reading the current source, that it's limited to a single repository. PH> The next step would be to work on package submission. If the centralized PH> system has a list of packages mapped to a list of DVCS repositories, PH> they could be polled periodically and all tags matching a certain PH> convention (say, starting with "v" and followed by a dotted number PH> series) would be treated as package. That version would then be PH> processed and published to a downloadable location for clients to pull PH> in. This should probably be a per-repository policy and process. PH> I wasn't thinking about integrating packages that Emacs already contains PH> until after these steps were complete. One thing that may be infeasible PH> but would certainly simplify things a lot would be if we spun off PH> packages like org-mode into their own separate DVCS repository and PH> removed them from the Emacs source tree before making package.el treat PH> them as packages. However, this may cause some unwanted chaos; I don't PH> want to barge in and create a lot of work for people. It might also PH> imply that network access would be necessary to perform a full build of PH> Emacs since it would have to download bundled packages at compilation PH> time. Not sure if that is a serious problem. I don't know about the other packages that come with Emacs, but Gnus could probably benefit from package.el-style installation (I don't speak for the Gnus project, though, so I can bring it up on the mailing list if necessary). A better setup process for Gnus would be really nice, though. The usual pre-install and post-install scripts you find in RPM or DEB would help. I suspect many other packages would benefit from a better setup process through package.el. Ted