From: Sebastian Rose <sebastian_rose@gmx.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Dan Davison <davison@stats.ox.ac.uk>,
Achim Gratz <Stromeko@nexgo.de>,
emacs-orgmode@gnu.org
Subject: Re: ELPA
Date: Tue, 28 Sep 2010 20:35:32 +0200 [thread overview]
Message-ID: <87aan1d8cr.fsf@gmx.de> (raw)
In-Reply-To: <87eicdiwsy.fsf@gmail.com> (Eric Schulte's message of "Tue, 28 Sep 2010 11:48:29 -0600")
"Eric Schulte" <schulte.eric@gmail.com> writes:
> I would think that it only makes sense to have one Org-mode package in
> ELPA, namely the bleeding edge git version of Org-mode. ELPA serves as
> a way to distribute packages which are not (or can't be) part of Emacs,
package.el in emacs-24 lists Org-mode as "built-in". That's the version
included in Emacs, not a package on elpa.gnu.org as I thought.
The "bleeding edge" package would be the only one there.
> I don't think it makes sense to use ELPA to re-distribute the version of
> Org-mode which users already have installed as part of their Emacs
> install. Un-installing the bleeding edge Org-mode would be equivalent
> to downgrading to the Emacs version.
+1
> Also, I would tend to think that this would make the most sense if we
> automate the ELPA integration s.t. every time a new revision is pushed
> up the to git repository, the ELPA version is automatically upgraded
> (with a git commit hook). If this isn't currently possible in ELPA then
> I'd agree with a point Jambunathan makes in this thread that this is a
> trick we can help ELPA to learn.
>
> The reason I think the above is important is that very frequently the
> answer to a question is "oh, I fixed that, please pull the latest from
> git", and we'll be constantly frustrating users if ELPA can't keep up
> with git.
>
> Best -- Eric
Sebastian
next prev parent reply other threads:[~2010-09-28 18:35 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
2010-09-28 14:55 ` Jambunathan K
2010-09-28 17:48 ` ELPA Eric Schulte
2010-09-28 18:35 ` Sebastian Rose [this message]
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=87aan1d8cr.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=Stromeko@nexgo.de \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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/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).