emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tftorrey@tftorrey.com (T.F. Torrey)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Mon, 09 Mar 2015 00:53:49 -0700	[thread overview]
Message-ID: <87y4n6txma.fsf@jack.tftorrey.com> (raw)
In-Reply-To: <87d24jqsj9.fsf@Rainer.invalid> (message from Achim Gratz on Sun, 08 Mar 2015 18:59:38 +0100)

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> It doesn't get any easier than it already is.  Having both a stable and
> an unstable version of Org avilable via ELPA is a non-starter for the
> simple reason that the package manager can't deal with the versioning
> problems this would introduce.

I think this is not only not a "non-starter", I think it is very easy
with the existing package manager.

The package manager can only handle one version of a package *per
archive*, so instead use one archive per version.

The current daily builds are here:

http://orgmode.org/elpa/

To allow choosing between stable (maint) and unstable (master), put the
package archives here instead:

Stable: http://orgmode.org/elpa-stable/

Unstable: http://orgmode.org/elpa-unstable/

Then, just add-to-list 'package-archives whichever flavor you want.

(And actually, to do away with the current conflict between the org and
org-plus-contrib packages, each of those should be in a separate
archive as well.)

If the next version of Emacs breaks Org out of core into the GNU ELPA
package archive, things can be even easier:  Keep the stable version in
the GNU package archive, and keep the unstable version in the archive on
the orgmode.org server.

(And personally, I think the "contrib" parts should either be merged
into the core or split into separate packages, but that's another can of
worms.)

All the best,
Terry
--
T.F. Torrey

  parent reply	other threads:[~2015-03-09  8:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 14:36 Bleeding edge in elpa Nikolai Weibull
2015-03-07 14:47 ` Xavier Maillard
2015-03-07 16:09   ` Nikolai Weibull
2015-03-08  5:48     ` Xavier Maillard
2015-03-09  9:08     ` Sebastien Vauban
2015-03-09 16:24       ` T.F. Torrey
2015-03-07 15:40 ` Grant Rettke
2015-03-07 21:44 ` T.F. Torrey
2015-03-08  1:32 ` Nicolas Girard
2015-03-08 14:17 ` Aaron Ecay
2015-03-08 17:24   ` Nikolai Weibull
2015-03-08 17:59     ` Achim Gratz
2015-03-08 18:34       ` Nikolai Weibull
2015-03-08 18:59         ` Rasmus
2015-03-09  6:48           ` T.F. Torrey
2015-03-10  1:57             ` Aaron Ecay
2015-03-10 21:30               ` T.F. Torrey
2015-03-11  2:51                 ` Aaron Ecay
2015-03-11 19:18                   ` T.F. Torrey
2015-03-11 19:59                     ` Nick Dokos
2015-03-09  7:53       ` T.F. Torrey [this message]
2015-03-09 18:24         ` Achim Gratz
2015-03-09 19:21           ` T.F. Torrey
2015-03-10 11:01             ` Alexis
2015-03-10 15:21               ` Grant Rettke
2015-03-08 18:09   ` T.F. Torrey
2015-03-08 19:57     ` Rasmus
2015-03-08 20:20       ` Achim Gratz
2015-03-08 20:27         ` Rasmus
2015-03-08 20:36           ` Achim Gratz
2015-03-09  8:13         ` T.F. Torrey
2015-03-09  7:31       ` T.F. Torrey
2015-03-10  2:01         ` Richard Y. Kim
2015-03-10  6:29           ` Achim Gratz
2015-03-10 21:21             ` T.F. Torrey
2015-03-10 20:20           ` T.F. Torrey
2015-08-05  0:00   ` Bastien Guerry
2015-03-10 10:51 ` Steinar Bang
2015-03-10 17:11   ` Achim Gratz

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=87y4n6txma.fsf@jack.tftorrey.com \
    --to=tftorrey@tftorrey.com \
    --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).