From: Chris Feng <chris.w.feng@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] externals/xelb ad879fb: Backport cl-defgeneric to Emacs 24
Date: Wed, 23 Sep 2015 09:08:36 +0800 [thread overview]
Message-ID: <CAP4=87He_C=R8kT-DDTP6PmwG07Dm3ERQjoHNEA2x9E8+5ufpg@mail.gmail.com> (raw)
In-Reply-To: <CAP4=87EBwy8jhU4e0oar+PzRsR_pcg4y5y6R9mhfiAU-JMoPQw@mail.gmail.com>
I released xelb in GNU ELPA but was surprised by the outcomes:
* I added cl-generic 0.2 as a dependency of xelb to make it working on
Emacs 24. But this causes a problem on Emacs 25: the builtin
cl-generic of version 1.0 is not listed in
`package--builtin-versions', so package.el would wrongly install
cl-generic 0.2 from GNU ELPA. Perhaps `package--builtin-versions'
should include cl-generic, or this variable would be useless since it
seems it's is only used in package.el.
* Due to a bug of EIEIO in Emacs 24, I cannot define classes with more
than 101 slots. Would it be possible to fix it in the next release of
Emacs 24 (by simply setting a fallback length of the obarray in
`eieio-defclass')?
* And finally a minor issue: README.org was picked as the long
description of this package. I personally consider org-mode files as
well as reStructuredText or other markup files, when not properly
rendered, are not easily readable. In fact I made this file mainly for
the GitHub project page and thought GNU ELPA would pick the
'Commentary:' section. Of course I can rename it to something not
mentioned in archive-contents.el to work around this problem.
Chris
next prev parent reply other threads:[~2015-09-23 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150920005618.18308.62122@vcs.savannah.gnu.org>
[not found] ` <E1ZdSvS-0004ly-Ut@vcs.savannah.gnu.org>
2015-09-20 15:25 ` [elpa] externals/xelb ad879fb: Backport cl-defgeneric to Emacs 24 Stefan Monnier
2015-09-21 5:11 ` Chris Feng
2015-09-23 1:08 ` Chris Feng [this message]
2015-09-23 13:36 ` Stefan Monnier
2015-09-23 13:56 ` Chris Feng
2015-09-23 15:59 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP4=87He_C=R8kT-DDTP6PmwG07Dm3ERQjoHNEA2x9E8+5ufpg@mail.gmail.com' \
--to=chris.w.feng@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).