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

[Stefan Monnier <monnier@iro.umontreal.ca>]

> I don't have a local clone of the ELPA repo, so this'd mean I couldn't
> do a clean build from Emacs source without going to some extra work.

If we move to include ELPA packages in the normal build (as Phillip is
trying to do), then "getting Emacs's Git" will indeed require getting
elpa.git as well.

IOW If we do that, then you will need to have a local clone (and the
extra work should be something similar to "make update-elpa").

> I think I'd feel more comfortable if we didn't impose this additional
> dependency on building Emacs. Can we arrange for that by moving the
> relevant code into Emacs proper?

Some packages don't want to live in emacs.git because they don't want to
be bound by Emacs's release schedule (and/or they want to make it easy
to synchronize changes with some external repository of that package).

For that reason, moving those into Emacs proper is not really desirable.

We could *copy* them into Emacs proper, but then we're stuck with the
problem of sync'ing changes between the copies, making it undesirable
as well.

> How much code are we talking about?

Not decided yet.  I suppose we'll start with just a couple packages, but
it's likely to grow to many packages.  But I think the expectation is
that Emacs's build should not break if ELPA packages are missing.


        Stefan