From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 22054@debbugs.gnu.org
Subject: bug#22054: Potential errors in package--builtins
Date: Tue, 1 Dec 2015 11:24:03 +0000 [thread overview]
Message-ID: <CAAdUY-JiX3+zBeDsnfcdF-LGCvqt4K8sZoaoiHOT4WyMeyr7_w@mail.gmail.com> (raw)
In-Reply-To: <87egf8d2wz.fsf@bernoul.li>
2015-11-29 19:24 GMT+00:00 Jonas Bernoulli <jonas@bernoul.li>:
> * `ielm' is missing from the list. I suspect it is not detected as a
> package because the first line does not contain the summary.
No. It needs a version number to be considered a package. But then,
why should it be on the list? Is it also provided in one of the
archives?
> Also, shouldn't the "interaction mode for Emacs Lisp" be located inside
> lisp/emacs-lisp/?
Last I was told, lisp/emacs-lisp is for libraries to be used by other
elisp code. But then, not all files in there perfectly fit that
description either.
So I'll let someone who cares about that continue this line of thought. =P
> * `cl-preload' is listed as a separate package.
>
> * `eieio-compat' is listed as a separate package. But I suspect that
> is intentional. Not sure though.
>
> * `sasl-scram-rfc' is listed as a separate package, but all the other
> `sasl-*' libraries are part of the `sasl' package.
Assuming you mean cl-preloadED.el... Maybe someone just fixed it but
none of these are listed as built-ins for me.
next prev parent reply other threads:[~2015-12-01 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 19:24 bug#22054: Potential errors in package--builtins Jonas Bernoulli
2015-12-01 11:24 ` Artur Malabarba [this message]
2015-12-03 14:46 ` Jonas Bernoulli
2015-12-03 15:18 ` Artur Malabarba
2015-12-03 15:37 ` Artur Malabarba
2015-12-12 19:43 ` Jonas Bernoulli
2015-12-12 20:34 ` 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
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=CAAdUY-JiX3+zBeDsnfcdF-LGCvqt4K8sZoaoiHOT4WyMeyr7_w@mail.gmail.com \
--to=bruce.connor.am@gmail.com \
--cc=22054@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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).