From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kyle Meyer <kyle@kyleam.com>
Cc: David Masterson <dsmasterson@outlook.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Orgguide missing in Org-9.3 package [9.3 (9.3-elpa @ /home/David/.emacs.d/elpa/org-9.3/)]
Date: Sat, 14 Dec 2019 15:52:03 +0100 [thread overview]
Message-ID: <87y2vfot7w.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871rt8rjrf.fsf@kyleam.com> (Kyle Meyer's message of "Fri, 13 Dec 2019 03:23:32 +0000")
Hello,
Kyle Meyer <kyle@kyleam.com> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Sorry, I don't have write access. But this issue seems to be about the
> Org ELPA tarball, so I don't understand how it'd be related to the
> recent Org sync with the Emacs repo.
That's because I misread the bug report and though it was related to
Emacs master branch.
In any case, Org ELPA tarball and files merged with Emacs are two
different things. IOW, even if ELPA tarball contains the Org guide, it
is not sufficient for Emacs to ship it, too. So this also needs to be
fixed on the Emacs' side, AFAIU.
> Checking the tarball at <https://elpa.gnu.org/packages/org-9.3.tar> as
> well as some recent ones at <https://orgmode.org/elpa/>, I didn't spot
> orgguide in any of them. And when I run `make elpa' from the Org repo,
> the tarball indeed seems to be missing the orgguide info file. Assuming
> there's not a good reason that orgguide is omitted, I think fixing this
> is just a matter of adding orgguide to server.mk's ORGELPA variable.
I have no objection, but, per above, we should check if there's
something to do in the Emacs repository, too.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-12-14 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 5:26 Bug: Orgguide missing in Org-9.3 package [9.3 (9.3-elpa @ /home/David/.emacs.d/elpa/org-9.3/)] David Masterson
2019-12-12 8:57 ` Nicolas Goaziou
2019-12-13 3:23 ` Kyle Meyer
2019-12-14 14:52 ` Nicolas Goaziou [this message]
2019-12-16 3:41 ` Kyle Meyer
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2vfot7w.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/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/org-mode.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).