From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: ELPA
Date: Tue, 28 Sep 2010 20:59:53 +0200 [thread overview]
Message-ID: <87iq1plmmu.fsf@Rainer.invalid> (raw)
In-Reply-To: 87eicdiwsy.fsf@gmail.com
"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.
I disagree and my vote is still on 'maint', i.e. what a user would be
most likely to install if he was visiting orgmode.org. Master changes
too often and might have experimental commits that later get reversed.
For anybody not following the mailing list this would be exactly the
wrong version to get through ELPA, especially since ELPA (at least in
standard configuration) does not notify about new versions.
> ELPA serves as a way to distribute packages which are not (or can't
> be) part of Emacs,
This is true of the current ELPA (tromey.com), but I feel the GNU ELPA
might take on an additional role: 1) easily obtaining packages that
would not normally come with the standard install of Emacs and 2)
keeping users updated on packages that are still developed and change
between releases. Org-mode would fall into the second category since it
will probably stay in the standard package set.
> 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.
Again, Emacs24 ELPA will be able to query multiple archives, something
that current ELPA can't. So Emacs24 will by default look at
elpa.gnu.org and users should be able to find the latest stable version
there (it may not show up exactly in the minute it is released on
orgmode.org). It should then be easy enough to configure ELPA (from
org-mode even?) to look for updates on orgmode.org first and get
bleeding edge from there if the user asks to do this. If GNU ELPA
adopts a different package update policy then both the stable and
bleeding edge version would need to be on orgmode.org -- has anybody had
a chance to ask or followed the discussion on the emacs.devel list?
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2010-09-28 19:00 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 ` ELPA Sebastian Rose
2010-09-28 18:59 ` Achim Gratz [this message]
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=87iq1plmmu.fsf@Rainer.invalid \
--to=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).