From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Phil Hagelberg Newsgroups: gmane.emacs.devel Subject: Re: Integrating package.el Date: Mon, 04 Jan 2010 21:02:24 -0800 Message-ID: <878wcdjg9r.fsf@hagelb.org> References: <878wclke6j.fsf@lifelogs.com> <87k4w5lbyb.fsf_-_@lifelogs.com> <87zl50jv52.fsf@lifelogs.com> <87d41rn3wt.fsf_-_@hagelb.org> <87k4vxiwlj.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262667921 26968 80.91.229.12 (5 Jan 2010 05:05:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 5 Jan 2010 05:05:21 +0000 (UTC) Cc: Ted Zlatanov , emacs-devel@gnu.org To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 05 06:05:14 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from terminus-est.gnu.org ([66.92.78.210] helo=lists.gnu.org) by lo.gmane.org with esmtp (Exim 4.50) id 1NS1bS-0007Z9-BU for ged-emacs-devel@m.gmane.org; Tue, 05 Jan 2010 06:05:10 +0100 Original-Received: from localhost ([127.0.0.1]:59347 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NS1bS-0008TY-5b for ged-emacs-devel@m.gmane.org; Tue, 05 Jan 2010 00:05:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NS1a4-0007RO-AZ for emacs-devel@gnu.org; Tue, 05 Jan 2010 00:03:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NS1Zg-0007Dt-0H for emacs-devel@gnu.org; Tue, 05 Jan 2010 00:03:43 -0500 Original-Received: from [199.232.76.173] (port=51810 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NS1Zf-0007Dl-Qp for emacs-devel@gnu.org; Tue, 05 Jan 2010 00:03:19 -0500 Original-Received: from caiajhbdccac.dreamhost.com ([208.97.132.202]:37748 helo=homiemail-a25.g.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NS1Zc-0006lh-DM for emacs-devel@gnu.org; Tue, 05 Jan 2010 00:03:19 -0500 Original-Received: from enigma (71-23-19-98.war.clearwire-wmx.net [71.23.19.98]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTPSA id 67D24678062; Mon, 4 Jan 2010 21:02:26 -0800 (PST) In-Reply-To: (Tom Tromey's message of "Mon, 04 Jan 2010 12:51:06 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:119413 Archived-At: Tom Tromey writes: >>>>>> "Ted" == Ted Zlatanov writes: > > Ted> Can package.el support that? It looks to me, from reading the current > Ted> source, that it's limited to a single repository. > > Yes, it is currently limited to a single repository. > This should not be too difficult to fix. I'm not sure why I left it out of my list of goals in my last email; this is definitely high on my priority list. I've also got a quick prototype of a DVCS-centric archive management tool (for gathering packages from library authors and publishing them) that I will post soon once I've fleshed it out a bit more. > Ted> I don't know about the other packages that come with Emacs, but Gnus > Ted> could probably benefit from package.el-style installation (I don't speak > Ted> for the Gnus project, though, so I can bring it up on the mailing list > Ted> if necessary). A better setup process for Gnus would be really nice, > Ted> though. The usual pre-install and post-install scripts you find in RPM > Ted> or DEB would help. I suspect many other packages would benefit from a > Ted> better setup process through package.el. > > If you want to try packaging it, I can explain what you need to do. > It is usually quite easy. I think in general this might be best done on an opt-in basis where the maintainer of a library indicates that they'd like to convert to a package and perhaps someone more familiar with package.el can help them integrate. -Phil