From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Kelvin White <kwhite@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: erc has lost its version number? (was: [elpa] ZNC package)
Date: Tue, 17 Feb 2015 14:09:47 -0200 [thread overview]
Message-ID: <CAAdUY-+xABbSSBjecam7-ZBMKzKKoicjR5XyuPX9FtFhj51HGA@mail.gmail.com> (raw)
In-Reply-To: <CAG-q9=YU=V-EM7j72DNkp+15-gi8d=6i6UsQJCw89OMyyyx8Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
> Is it as simple as a header with the version number, or does `erc-version'
> need to respond with 5.3?
Yes, a header with the version number is enough. `erc-version' is
irrelevant to package.el.
> > We need to either ask these packages to rely on Emacs version instead
> > of erc version, or come up with a way to indicate that a package
> > should inherit emacs' version number, or go back to specifying erc's
> > version.
>
> I think we should definitely ask these packages to not rely on
erc-version 5.3, but we can also try and keep the obsolete version number
around until it doesn't break other packages.
Ok, let's bring back the number for now. I'll try to get in touch with the
authors.
I think it would be a useful feature for built-in packages to be able to
specify "follow emacs version". This could be as simple as specifying
"emacs" on the Version header (instead of a version number).
[-- Attachment #2: Type: text/html, Size: 1096 bytes --]
next prev parent reply other threads:[~2015-02-17 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 15:11 erc has lost its version number? (was: [elpa] ZNC package) Kelvin White
2015-02-17 16:09 ` Artur Malabarba [this message]
2015-02-17 19:15 ` Kelvin White
2015-02-17 19:56 ` erc has lost its version number? Tom Tromey
2015-02-17 23:38 ` Artur Malabarba
-- strict thread matches above, loose matches on Subject: below --
2015-02-16 13:16 erc has lost its version number? (was: [elpa] ZNC package) Artur Malabarba
2015-02-16 14:13 ` Kelvin White
2015-02-17 10:36 ` 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=CAAdUY-+xABbSSBjecam7-ZBMKzKKoicjR5XyuPX9FtFhj51HGA@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kwhite@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.