From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tom Tromey <tromey@redhat.com>,
phil@hagelb.org, rms@gnu.org, Stephen Eilert <spedrosa@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Emacs Package Management
Date: Thu, 17 Sep 2009 10:58:17 -0400 [thread overview]
Message-ID: <1253199497.4770.1092.camel@projectile.siege-engine.com> (raw)
In-Reply-To: <jwvskel1yjc.fsf-monnier+emacs@gnu.org>
On Thu, 2009-09-17 at 09:43 -0400, Stefan Monnier wrote:
> Stephen> ELPA is a nice starting point. But I think it is
> Stephen> disproportionally easy to download packages, as opposed to
> Stephen> submitting them. For single files, I would very much like to
> Stephen> have a M-x submit-package, and have it do anything required to
> Stephen> upload it, adding licenses and so on.
>
> > Yeah. I would like this too, but that would mean finding time to write
> > the web app and everything else :-)
>
> 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, ...).
EDE builds makefiles that builds dist files for projects. CEDET's
distribution files are fabricated by EDE's code generator. If there
were to be a "preferred" Emacs Lisp project style, EDE would be able to
handle it easily as a wrapper on top of whatever the preferred
implementation is, or you can use the same pattern that CEDET uses now.
Eric
next prev parent reply other threads:[~2009-09-17 14:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 21:27 Emacs Package Management Stephen Eilert
2008-08-01 22:58 ` Tom Tromey
2008-08-01 23:14 ` Phil Hagelberg
2008-08-01 23:25 ` Lennart Borgman (gmail)
2008-08-02 0:13 ` Tom Tromey
2008-08-03 1:33 ` Richard M. Stallman
2008-08-03 18:03 ` Stefan Monnier
2008-08-04 15:33 ` Richard M. Stallman
2008-08-04 19:07 ` Stefan Monnier
2008-08-05 8:04 ` Richard M. Stallman
2008-08-05 13:09 ` Stephen Eilert
2008-08-05 14:39 ` Paul R
2008-08-06 3:35 ` Richard M. Stallman
2009-09-16 22:36 ` Stephen Eilert
2009-09-17 1:44 ` Tom Tromey
2009-09-17 13:43 ` Stefan Monnier
2009-09-17 14:26 ` Tom Tromey
2009-09-17 14:58 ` Eric M. Ludlam [this message]
2009-09-28 21:13 ` Phil Hagelberg
2009-09-28 21:48 ` Lennart Borgman
2009-09-28 21:54 ` Chong Yidong
2009-09-28 22:30 ` Phil Hagelberg
2009-09-29 11:31 ` Richard Stallman
2009-09-29 19:18 ` Stefan Monnier
2009-09-29 19:41 ` Tom Tromey
2009-09-30 1:20 ` Stefan Monnier
2009-09-30 2:07 ` Tom Tromey
2009-09-30 4:39 ` Stefan Monnier
2009-09-30 20:18 ` Tom Tromey
2009-10-01 5:01 ` Stefan Monnier
2008-08-02 1:58 ` Stephen Eilert
2008-08-02 3:36 ` Tom Tromey
2008-08-02 17:30 ` Richard M Stallman
2008-08-12 4:10 ` Thomas Lord
2009-09-12 22:38 ` Phil Hagelberg
2009-09-12 23:30 ` Eric M. Ludlam
2009-09-13 16:40 ` Richard Stallman
2009-09-14 9:07 ` joakim
2009-09-14 9:26 ` David Kastrup
2009-09-15 7:16 ` Richard Stallman
2009-09-15 8:30 ` Miles Bader
2009-09-15 18:15 ` Richard Stallman
2009-09-15 18:58 ` Tom Tromey
2009-09-15 22:08 ` Miles Bader
2009-09-16 15:16 ` Richard Stallman
2009-09-16 18:41 ` Stefan Monnier
2009-09-17 1:05 ` Geoff Gole
2009-09-17 19:50 ` Richard Stallman
2009-09-15 18:55 ` Tom Tromey
2009-09-17 6:37 ` Richard Stallman
2009-09-17 8:28 ` Tassilo Horn
2009-09-17 8:37 ` joakim
2009-09-17 8:48 ` Lennart Borgman
2009-09-17 9:31 ` Tassilo Horn
2009-09-17 10:43 ` Lennart Borgman
2009-09-17 11:50 ` Rupert Swarbrick
2009-09-19 2:40 ` Bob Rogers
2009-09-19 12:10 ` Rupert Swarbrick
2009-09-17 14:24 ` Tom Tromey
2009-09-17 19:22 ` Tassilo Horn
2009-09-17 15:04 ` Eric M. Ludlam
2009-09-17 13:46 ` Stefan Monnier
2009-09-17 14:21 ` Tom Tromey
2009-09-13 17:00 ` Eric Schulte
2008-08-02 14:46 ` Paul R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1253199497.4770.1092.camel@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phil@hagelb.org \
--cc=rms@gnu.org \
--cc=spedrosa@gmail.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).