[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using Org as the source format to generate org.texi

From: Phillip Lord
Subject: Re: Using Org as the source format to generate org.texi
Date: Sat, 10 Mar 2018 20:07:57 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.91 (gnu/linux)

Achim Gratz <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]