From: David Kastrup <dak@gnu.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Adding to ELPA?
Date: Mon, 12 Oct 2015 07:56:54 +0200 [thread overview]
Message-ID: <8737xgd3yx.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAdUY-JgucN_VeVsqKVPZBW-=CB7Kx0Qq4JHWAW9bRW2dHb7_A@mail.gmail.com> (Artur Malabarba's message of "Mon, 12 Oct 2015 00:15:02 +0100")
Artur Malabarba <bruce.connor.am@gmail.com> writes:
> On 11 Oct 2015 7:09 pm, "David Kastrup" <dak@gnu.org> wrote:
>> > Couldn't you distribute the package with it?
>>
>> It does not really make all that much sense since this package is a
>> generic MIDI input package with lots of potential uses, [...]
>
> Sorry, I should have expressed myself better. I meant momentarily, while we
> wait for 25 to be released.
> I agree this is a nice package, and should be generally available.
>
> I'm just thinking your users are going to try to install the package
> and it's going to fail because of the 25 dep, and then they're going
> to Google for Emacs 25 and won't find it.
There are a number of packages in ELPA with an Emacs 25 dependency.
packages/el-search/el-search.el:;; Package-Requires: ((emacs "25"))
packages/iterators/iterators.el:;; Package-Requires: ((emacs "25"))
packages/svg/svg.el:;; Package-Requires: ((emacs "25"))
What makes them different?
--
David Kastrup
next prev parent reply other threads:[~2015-10-12 5:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 15:28 Adding to ELPA? David Kastrup
2015-10-10 7:08 ` Artur Malabarba
2015-10-10 7:50 ` David Kastrup
2015-10-10 22:07 ` Artur Malabarba
2015-10-11 16:57 ` David Kastrup
2015-10-11 17:47 ` Artur Malabarba
2015-10-11 18:09 ` David Kastrup
2015-10-11 23:15 ` Artur Malabarba
2015-10-12 5:56 ` David Kastrup [this message]
2015-10-12 7:58 ` Artur Malabarba
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=8737xgd3yx.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=bruce.connor.am@gmail.com \
--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.