From: Bastien <bzg@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: GNU ELPA security and Org-mode
Date: Mon, 30 Apr 2018 15:55:37 +0200 [thread overview]
Message-ID: <87muxkztly.fsf@gnu.org> (raw)
In-Reply-To: <jwvd0yg6cdv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 30 Apr 2018 09:42:47 -0400")
Thanks for the feedback.
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> - I create the "elpa/packages/org" directory in this branch.
>
> No. It should contain the same files with the same names as the
> tarball would.
Not sure here.
Do you mean elpa.git should contain
elpa/packages/org-20180430/org.el
elpa/packages/org-20180430/org-table.el
etc.?
>> - I copy the content of an Org ELPA archive (eg org-20180430.tar)
>> into this directory, with org-{version|pkg|loaddefs}.el files.
>
> Yes, except for org-pkg.el (the corresponding info should be in org.el
> instead).
Because org-pkg.el is generated by elpa/GNUmakefile, right?
If so, why adding org-loaddefs.el since org-autoloads.el would also be
autogenerated?
And would org-version.el still be required?
Or the package version would just be extracted from the org.el
"Version: 9.1.12" keyword?
If possible, I'd like to not add org-loaddefs.el and org-version.el
and have org-autoloads.el and the package version autogenerated like
for any other package.
--
Bastien
next prev parent reply other threads:[~2018-04-30 13:55 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 [this message]
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
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=87muxkztly.fsf@gnu.org \
--to=bzg@gnu.org \
--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).