unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: GNU ELPA security and Org-mode
Date: Mon, 30 Apr 2018 10:18:19 -0400	[thread overview]
Message-ID: <jwvpo2g4wcy.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 87a7tkzswv.fsf@gnu.org

>> If so, why adding org-loaddefs.el since org-autoloads.el would also be
>> autogenerated?
>> And would org-version.el still be required?

I don't really know precisely what those files are about, but to the
extent that they're specific to Org, I don't see any reason to treat
them differently from any other org*.el file here.

AFAIK org-loaddefs.el is supposed to only be loaded when org-mode is
activated, whereas org-autoloads.el is loaded at Emacs start up (so it
should mostly contain an autoload for `org-mode` itself).

The elpa.gnu.org scripts will not look for the package's version in
org-version.el but in org.el's "Version:" header, but presumably
org-version.el is used by Org, so it's probably still useful (tho Org
could be changed to look for the corresponding info in org.el's
"Version:" header as well).


        Stefan




  reply	other threads:[~2018-04-30 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 15:04 GNU ELPA security and Org-mode Stefan Monnier
2018-04-28 11:19 ` Bastien
2018-04-30  2:15   ` Stefan Monnier
2018-04-30  7:13     ` Bastien
2018-04-30 12:29       ` Stefan Monnier
2018-04-30 13:34         ` Bastien
2018-04-30 13:42           ` Stefan Monnier
2018-04-30 13:52             ` Stefan Monnier
2018-04-30 13:55             ` Bastien
2018-04-30 14:00               ` Stefan Monnier
2018-04-30 14:07                 ` Bastien
2018-04-30 16:37                   ` Stefan Monnier
2018-05-01  8:07                     ` Bastien
2018-04-30 14:10               ` Bastien
2018-04-30 14:18                 ` Stefan Monnier [this message]
2018-04-30 15:18                   ` Bastien
2018-04-30 15:37                     ` Stefan Monnier
2018-05-01  8:07                       ` Bastien

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=jwvpo2g4wcy.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).