From: phillip.lord@russet.org.uk (Phillip Lord)
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Using Org as the source format to generate org.texi
Date: Sat, 10 Mar 2018 20:07:57 +0000 [thread overview]
Message-ID: <87vae3zobm.fsf@russet.org.uk> (raw)
In-Reply-To: <87fu59qhbd.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 09 Mar 2018 18:39:34 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Glenn Morris writes:
>> Note that this will make info generation depend on the existence of
>> src/emacs, when it was previously independent.
>
> Well, you could certainly define a separate Emacs instance to be used
> for the generation of the documentation unless you do a full greenfield
> bootstrap.
I think that's not a good idea, but I don't think it's necessary. Having
info dependent on src/emacs might slow the build somewhat. It's easiest
enough to test.
>> Also, if any other manual made the same change, it would prevent
>> bootstrapping Emacs without Org present (eg if the idea to include elpa
>> packages in Emacs releases ever goes anywhere, and it's desired to stop
>> duplicating Org in the Emacs repo; an idea which still makes complete
>> sense to me).
>>
>> (Just trying to list some items relevant to the "other tweaking" part.)
>
> I'd say that it just changes the way how the bootstrap is done, I don't
> yet see it preventing anything. The same line of argumentation needs to
> be followed for the tarball generation.
As it happens I have a version of this now. It would lead to the
slightly strange situation that the build would refer to org-mode
functions which are not actually hosted in the repo. So, it would mean
that you could not build Emacs from a clean clone of the Emacs repo
without access to the ELPA repo (i.e. a local clone).
In practice, I suspect this would not be a huge issue.
Phil
next prev parent reply other threads:[~2018-03-10 20:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 18:04 Using Org as the source format to generate org.texi Bastien
2018-03-06 20:20 ` Stefan Monnier
2018-03-06 20:24 ` Kaushal Modi
2018-03-06 21:54 ` Achim Gratz
2018-03-07 0:22 ` Bastien
2018-03-07 17:43 ` Eli Zaretskii
2018-03-07 17:52 ` Kaushal Modi
2018-03-08 10:04 ` Bastien Guerry
2018-03-08 7:28 ` Michael Albinus
2018-03-08 10:06 ` Bastien Guerry
2018-03-08 10:13 ` Bastien Guerry
2018-03-07 17:39 ` Glenn Morris
2018-03-07 22:57 ` Richard Stallman
2018-03-09 11:30 ` Bastien
2018-03-10 21:26 ` Nicolas Goaziou
2018-03-11 3:40 ` Eli Zaretskii
2018-03-11 14:59 ` Michael Albinus
2018-03-11 18:13 ` Nicolas Goaziou
2018-03-11 23:26 ` Richard Stallman
2018-03-12 14:07 ` Nicolas Goaziou
2018-03-12 15:51 ` Eli Zaretskii
2018-03-12 16:42 ` Nicolas Goaziou
2018-03-12 17:32 ` Eli Zaretskii
2018-03-12 17:57 ` Nicolas Goaziou
2018-03-12 20:16 ` Eli Zaretskii
2018-03-12 21:37 ` Nicolas Goaziou
2018-03-13 15:55 ` Eli Zaretskii
2018-03-13 17:24 ` Nicolas Goaziou
2018-03-13 17:43 ` Eli Zaretskii
2018-03-13 21:37 ` Nicolas Goaziou
2018-04-14 17:10 ` @key{...} mis-use (was: Using Org as the source format to generate org.texi) Nicolas Goaziou
2018-04-19 9:22 ` Eli Zaretskii
2018-03-06 21:30 ` Using Org as the source format to generate org.texi Paul Eggert
2018-03-07 0:19 ` Bastien
2018-03-07 1:08 ` Paul Eggert
2018-03-07 7:33 ` Achim Gratz
2018-03-09 17:52 ` Achim Gratz
2018-03-09 18:02 ` Paul Eggert
2018-03-09 18:23 ` Achim Gratz
2018-03-07 17:41 ` Glenn Morris
2018-03-09 11:19 ` Phillip Lord
2018-03-12 17:12 ` Glenn Morris
2018-03-09 17:39 ` Achim Gratz
2018-03-10 20:07 ` Phillip Lord [this message]
2018-03-11 3:00 ` Paul Eggert
2018-03-11 3:55 ` Stefan Monnier
2018-03-11 21:46 ` Phillip Lord
2018-03-12 21:04 ` Radon Rosborough
2018-03-13 9:10 ` Phillip Lord
2018-03-13 12:29 ` Stefan Monnier
2018-03-13 16:47 ` Phillip Lord
2018-04-14 19:15 ` Joshua Branson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vae3zobm.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=Stromeko@nexgo.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.