From: Jonas Bernoulli <jonas@bernoul.li>
To: 14010@debbugs.gnu.org
Subject: bug#14010: 24.3; builtin libraries that should specify the package
Date: Fri, 14 Mar 2014 03:02:45 +0100 [thread overview]
Message-ID: <87txb1pmey.fsf@bernoul.li> (raw)
In-Reply-To: <877gl1n56y.fsf@bernoul.li>
Jonas Bernoulli wrote:
>> The packages python, grep, cpp and compile don't appear in
>> package--builtins because the "Package" header keyword isn't defined
>> in the respective libraries. I think it would make sense for these
>> to be treated as separate packages.
Glenn Morris wrote:
> But all four do appear in package--builtins?
(The variable is now called package--builtin-versions.)
python does indeed appear in the value of package--builtin-versions.
Maybe that was already the case when I originally reported otherwise.
While python.el still does not define the "Package" header keyword, it
does define "Version". And that is enough for it to be considered a
package (see autoload-generate-file-autoloads).
However grep, cpp and compile still do not appear there.
next prev parent reply other threads:[~2014-03-14 2:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 21:15 bug#14010: 24.3; builtin libraries that should specify the package Jonas Bernoulli
2013-05-14 7:52 ` Glenn Morris
2014-03-14 2:02 ` Jonas Bernoulli [this message]
2014-03-14 7:59 ` Glenn Morris
2014-03-14 12:44 ` Jonas Bernoulli
2014-03-14 16:10 ` Glenn Morris
2014-03-14 17:55 ` Glenn Morris
[not found] ` <handler.14010.D14010.13948197375939.notifdone@debbugs.gnu.org>
2014-03-14 18:26 ` bug#14010: closed (Re: bug#14010: 24.3; builtin libraries that should specify the package) Jonas Bernoulli
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=87txb1pmey.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=14010@debbugs.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 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).