From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: Require Emacs >=24.3 for next Org versions?
Date: Mon, 17 Aug 2015 07:24:11 +0200 [thread overview]
Message-ID: <87oai6lc78.fsf@Rainer.invalid> (raw)
In-Reply-To: CAAdUY-LnRG6qRACtdi4+6juHkrrqyyJ5d1VUk7HBv9Kg0N14uw@mail.gmail.com
Artur Malabarba writes:
>> Now, even if we did keep an Emacs 23 compatible Org around (most likely
>> being feature frozen and only getting critical bugfixes) we'd still have
>> to solve the problem that Emacs' package manager currently can't serve
>> different packages for different versions of Emacs.
>
> Emacs 23 didn't come with package.el, which means you're targetting
> people who have manually added package.el to their system. I think
> it's safe to assume that this group of people is capable of manually
> downloading and setting up your compatibility org version. Just make
> sure it's very visible and easy to find when searched for.
For someone savvy enough wanting to install a newer Org on Emacs 23 I
expect a good proportion to recognize also that installing package
manager for Emacs 23 first is a good way to also update the other eLisp
they have on their systems. However, that's not the issue I was
commenting about.
The issue, which admittedly doesn't really have much to do with Org and
was meant as a side remark, still stands that package manager can't
install different packages or package versions for different Emacs
versions. If you wanted to do that, you'd need to create an ELPA
archive for each version of Emacs and teach people to use the right one
for the version they currently use. That strikes me as odd.
At least the last part could be solved by optionally having a
version-specific sub-structure in ELPA and have Emacs' package manager
look there first. I tend to the idea that each such sub-structure
should be a complete package archive, based on the assumption that it
would be served from a system that knows about (hard-)links or virtual
directories (that is the webserver rewrites the request to use some
other directory if it can't find it in the one you were looking).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2015-08-17 5:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 8:47 Require Emacs >=24.3 for next Org versions? Bastien Guerry
2015-08-15 23:01 ` Richard Stallman
2015-08-16 5:07 ` Andrés Ramírez
2015-08-16 5:38 ` Bozhidar Batsov
2015-08-16 6:35 ` Achim Gratz
2015-08-16 6:27 ` Achim Gratz
2015-08-16 9:54 ` Artur Malabarba
2015-08-16 13:14 ` Richard Stallman
2015-08-16 13:45 ` David Kastrup
2015-08-16 14:52 ` Artur Malabarba
2015-08-17 5:04 ` Richard Stallman
2015-08-17 5:24 ` Achim Gratz [this message]
2015-08-18 3:41 ` Richard Stallman
2015-08-16 13:13 ` Richard Stallman
2015-08-16 13:13 ` Richard Stallman
2015-08-17 2:16 ` Stephen J. Turnbull
2015-08-18 23:09 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oai6lc78.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.