From: Dan Davison <davison@stats.ox.ac.uk>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: ELPA [WAS] Re: [PROPOSAL] Quick and easy installation instructions
Date: Sun, 26 Sep 2010 21:57:00 +0100 [thread overview]
Message-ID: <87iq1srzoj.fsf_-_@stats.ox.ac.uk> (raw)
In-Reply-To: <87tylce24o.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 26 Sep 2010 21:27:51 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> Dan Davison <davison@stats.ox.ac.uk> writes:
>> OK, so we're agreed. But your points below don't seem to describe a less
>> technical route. Could you describe the less technical version of the
>> instructions for the method that you are advocating?
>
> Installing is something technical and I'm a tech-head, so you're asking
> something of me I'm not really qualified to do. :-)
>
> My points were:
>
> - I think that a proper installation via make is the way to go, but I
> recognize that some folks don't want or need to do that.
>
> - There is a default place where Emacs expects this kind of stuff and
> has some magic implemented to make it work without further
> configuration, and that place is site-lisp. You can put it someplace
> else, but then you have to alter the load-path or you are at the mercy
> of some special configuration to make the same magic work in other
> places, too (I've had ~/lisp set up that way when I was still
> compiling Emacs myself).
>
> - If org was delivered and compiled in 'org/' rather than 'lisp/', one
> could instruct users to just take that folder and copy/drag it into
> the site-lisp directory of their Emacs installation. You can do that
> with the lisp folder, but I'd at least tell people to please rename it
> to org after doing the copy.
>
> If you want to get any less technical than that, I'd suggest ELPA or
> something like it (as has been discussed already in another thread).
> ELPA packages build and configure themselves as far as possible, so that
> should take out the guesswork for novice users. Also it looks like it
> will come standard with Emacs24 (with a GNU archive and the possibility
> to add additional archives, which could take care of the "bleeding
> edge"), so there will be absolutely no "installation" work required from
> the user from then on.
Hi Achim,
Thanks, that was very helpful.
Using ELPA does seem like an attractive route, especially if it
(package.el) is going to be in Emacs24.
- How much work would it take to put and maintain Org-mode on ELPA?
- Would it make sense to have two different packages available via ELPA,
i.e. Latest Release and Latest?
- Will it be possible for the Org project to have control over the files
that ELPA points at (in which case we might be able to keep the latest
updated a few times a day or something), or do we have to submit them
to a server that's out of our control?
- Will ELPA be able to get the info files installed suitably?
Dan
>
>
> Regards,
> Achim.
next prev parent reply other threads:[~2010-09-26 20:57 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 ` Dan Davison [this message]
2010-09-28 10:52 ` ELPA [WAS] " Scot Becker
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=87iq1srzoj.fsf_-_@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=Stromeko@nexgo.de \
--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).