From: Scot Becker <scot.becker@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: ELPA [WAS] Re: [PROPOSAL] Quick and easy installation instructions
Date: Tue, 28 Sep 2010 11:52:34 +0100 [thread overview]
Message-ID: <AANLkTimFO1+SxycrmaqNUCo1B1bTcR5ZF6DVn8Kw6rbf@mail.gmail.com> (raw)
In-Reply-To: <87iq1srzoj.fsf_-_@stats.ox.ac.uk>
Dan,
I have no special expertise on this, but I'll hazzard an answer as a
simple ELPA user:
> Using ELPA does seem like an attractive route, especially if it
> (package.el) is going to be in Emacs24.
To me too, ELPA is a great idea. It probably needs some perfecting,
but if it works for these purposes, we only help the perfecting by
encouraging it's use.
> - How much work would it take to put and maintain Org-mode on ELPA?
I'll let someone else answer that, but I'd be suprised if it couldn't
be automated.
> - Would it make sense to have two different packages available via ELPA,
To me, yes. I like using git for the development tree, but I expect
that ELPA makes for a nice way for Windows users (and others who don't
want to or can't use git) to get the latest version easily (and
possibly even to downgrade if necessary). The latest release version
is of course necessary as well, since using it is the main
recommendation to new users.
> - Will it be possible for the Org project to have control over the files
An excellent and important question. We'd rather not be dependent on
personal intervention from others to update, especially the '-latest'
version. And even for the releases, we'd probably be glad to see them
propagate to the repository pretty quickly. (The current non-gnu ELPA
repo only updates every two weeks or so. This is fine for many
projects, but probably not enough even for org-mode releases.)
> - Will ELPA be able to get the info files installed suitably?
In principle, yes. ELPA does concern itself with both the load-path
and the info-path.
Scot
next prev parent reply other threads:[~2010-09-28 10:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 13:33 [PROPOSAL] Quick and easy installation instructions Dan Davison
2010-09-26 13:44 ` Thomas S. Dye
2010-09-26 13:52 ` A. Ryan Reynolds
2010-09-26 14:21 ` Richard Riley
2010-09-26 14:52 ` Dan Davison
2010-09-26 15:01 ` Carsten Dominik
2010-09-26 15:02 ` Richard Riley
2010-09-26 21:00 ` Rémi Vanicat
2010-09-27 6:23 ` Richard Riley
2010-09-26 20:51 ` Adam
2010-09-26 14:51 ` John Hendy
2010-09-26 17:37 ` Achim Gratz
2010-09-26 18:22 ` Dan Davison
2010-09-26 19:27 ` Achim Gratz
2010-09-26 20:57 ` ELPA [WAS] " Dan Davison
2010-09-28 10:52 ` Scot Becker [this message]
2010-09-28 14:55 ` Jambunathan K
2010-09-28 17:48 ` ELPA Eric Schulte
2010-09-28 18:35 ` ELPA Sebastian Rose
2010-09-28 18:59 ` ELPA Achim Gratz
2010-09-28 19:09 ` ELPA Richard Riley
2010-09-28 20:43 ` ELPA Scot Becker
2010-09-27 6:26 ` [PROPOSAL] Quick and easy installation instructions Carsten Dominik
2010-09-27 9:00 ` Dan Davison
2010-09-27 9:55 ` Carsten Dominik
2010-09-27 10:50 ` Giovanni Ridolfi
2010-09-27 12:55 ` Sebastian Rose
2010-09-27 13:53 ` Dan Davison
2010-09-27 14:06 ` Sebastian Rose
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimFO1+SxycrmaqNUCo1B1bTcR5ZF6DVn8Kw6rbf@mail.gmail.com \
--to=scot.becker@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).