From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Emacs Package Management Date: Mon, 28 Sep 2009 23:48:36 +0200 Message-ID: References: <485b0c380808011427n4d3144eey3f8daf3abac83bf4@mail.gmail.com> <485b0c380808050609y56042595l42a5bb05b34458f0@mail.gmail.com> <485b0c380909161536t331a71fdg1c45150c418b72b2@mail.gmail.com> <87ab0eai3l.fsf@hagelb.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1254174560 20363 80.91.229.12 (28 Sep 2009 21:49:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Sep 2009 21:49:20 +0000 (UTC) Cc: Tom Tromey , emacs-devel@gnu.org, Stefan Monnier , Stephen Eilert , rms@gnu.org To: Phil Hagelberg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 28 23:49:12 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 1MsO5m-0001DR-Qa for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2009 23:49:11 +0200 Original-Received: from localhost ([127.0.0.1]:42284 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsO5m-0001jk-89 for ged-emacs-devel@m.gmane.org; Mon, 28 Sep 2009 17:49:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MsO5h-0001jf-8D for emacs-devel@gnu.org; Mon, 28 Sep 2009 17:49:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MsO5b-0001jQ-Ot for emacs-devel@gnu.org; Mon, 28 Sep 2009 17:49:04 -0400 Original-Received: from [199.232.76.173] (port=58146 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MsO5b-0001jN-MZ for emacs-devel@gnu.org; Mon, 28 Sep 2009 17:48:59 -0400 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:35617) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MsO5a-0007FB-4V; Mon, 28 Sep 2009 17:48:58 -0400 Original-Received: by ywh32 with SMTP id 32so5217815ywh.14 for ; Mon, 28 Sep 2009 14:48:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=IkVB17LO41XXmhhUcSQYCwEM+W/jwQdW8GDxUVTFgMY=; b=jOtl7kqQjZZfytdO3E+k9mczoepBul5r+Zy1HEoSO9EXhdjtAmZM3iFJaflt9BM/Ll qEy5otXP0sbCCPCMFcJ3Ixhpb9OCbkby/2p0y2ineoXUM7OtRJtNxA4u/x+7mJ3/KYTh VFRmiGP23eEydkwMFt6a0B8KbjOsXp2mKqAJs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=QZE3WIKuZGKqyAGNhG6k48xtDi+ooDfkImrofaB48GzdmT7GqDQwK7h6saC0WM9m0G VrgF1vnw82vCfFcUXKsrEqUkKLHadO2yHvlXI5GWzzz1gRMfHS/H1vWwYKSjkzzXjbzF y+0bEECmm6LF9/govmyfTMsrGgEov+gmZA7Fw= Original-Received: by 10.101.56.11 with SMTP id i11mr3683540ank.5.1254174536595; Mon, 28 Sep 2009 14:48:56 -0700 (PDT) In-Reply-To: <87ab0eai3l.fsf@hagelb.org> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:115743 Archived-At: On Mon, Sep 28, 2009 at 11:13 PM, Phil Hagelberg wrote: > Stefan Monnier writes: > >> For the FSF-hosted repository of packages, I'd want all the packages >> to be version controlled, so the "submit-package" would be nothing else >> than "bzr commit" (but yes, some extra code would need to be written to >> automatically build a tarball out of the newly committed code, ...). >> >>> Yes, this is something that package.el provides. =C2=A0One thing that w= ould >>> be nice is to have Emacs also advertise the packages it provides -- tha= t >> >> Indeed, we'd of course want that, if/once we provide such >> a package system. =C2=A0But that should be easy. > > It seems like though there are a few questions remaining about policies > for submissions, there's a general consensus that Emacs should get a > packaging system, probably based on package.el with some enhancements > for submitting projects. > > I'd like to start brainstorming as to what this would look like. > > 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. > > Thoughts? I think the way to go is to use a source code management system. However I wonder if it would not be better with one project. That would allow some structure to it. The drawback is that some management have to be done and maybe it looses the "everyone" can put something there thing then. Perhaps structure can be combined with this somewhere else? Maybe as a separate project that is a layer between the package system and the package projects?