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: Emacs Package Management Date: Mon, 28 Sep 2009 15:30:00 -0700 Message-ID: <87ab0e8zyv.fsf@hagelb.org> References: <485b0c380808011427n4d3144eey3f8daf3abac83bf4@mail.gmail.com> <87ej589vku.fsf@hagelb.org> <485b0c380808050609y56042595l42a5bb05b34458f0@mail.gmail.com> <485b0c380909161536t331a71fdg1c45150c418b72b2@mail.gmail.com> <87ab0eai3l.fsf@hagelb.org> <87eipqpwfi.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1254177030 27082 80.91.229.12 (28 Sep 2009 22:30:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Sep 2009 22:30:30 +0000 (UTC) Cc: Tom Tromey , emacs-devel@gnu.org, Stefan Monnier , Stephen Eilert , rms@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 29 00:30:22 2009 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 1MsOje-0004KP-Cb for ged-emacs-devel@m.gmane.org; Tue, 29 Sep 2009 00:30:22 +0200 Original-Received: from localhost ([127.0.0.1]:58427 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsOjd-0003S6-FZ for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2009 18:30:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MsOjW-0003Rm-Ke for emacs-devel@gnu.org; Mon, 28 Sep 2009 18:30:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MsOjS-0003Qr-St for emacs-devel@gnu.org; Mon, 28 Sep 2009 18:30:14 -0400 Original-Received: from [199.232.76.173] (port=54086 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsOjS-0003Qi-KN for emacs-devel@gnu.org; Mon, 28 Sep 2009 18:30:10 -0400 Original-Received: from caiajhbdcbef.dreamhost.com ([208.97.132.145]:44701 helo=homiemail-a15.g.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MsOjO-0005wK-IV; Mon, 28 Sep 2009 18:30:06 -0400 Original-Received: from enigma (96-26-232-193.sea.clearwire-dns.net [96.26.232.193]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by homiemail-a15.g.dreamhost.com (Postfix) with ESMTPSA id 83BC076C06A; Mon, 28 Sep 2009 15:30:02 -0700 (PDT) In-Reply-To: <87eipqpwfi.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 28 Sep 2009 17:54:25 -0400") 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:115752 Archived-At: Chong Yidong writes: >> One way to do it would be to have every package register as a Savannah >> project, and have some kind of operation (probably implemented as an >> elisp function) that could produce the static files that package.el >> consumes and place them in a publicly accessible http-served >> directory. Making package releases correspond with VCS tags would >> simplify things, so with some kind of post-commit hooks Savannah could >> run this function whenever a tag is updated in the project. >> >> This would require very few changes to package.el. Writing such a >> function should not be difficult. The only question is how easy it would >> be to get Savannah to run it at the right time. > > We're not necessarily restricted to Savannah; if necessary, we might be > able to use the gnu.org ftp servers, and their mirrors (which we > currently already use for distributing the monolithic tarball, after > all). I think Stefan had a great point that a lot of complexity involving user, project, and release management can be sidestepped by using the existing infrastructure of a version-control system. Savannah seems to be a good fit for this, but if we can host an Emacs-package-specific VCS somewhere else, that would work too. -Phil