Re: Core ELPA was: Testing fontification, indentation, and buffer manipulation

[Phillip Lord]

Stefan Monnier <address@hidden> writes:

>>> Also, as a general rule, for technical reasons as well as for privacy
>>> reasons we consider it important not to initiate network connections
>>> unless the user explicitly requested that network connection.
>>> [ Same reason why Emacs doesn't offer to auto-update packages at
>>>   startup.  ]
>>
>> Yes, indeed, I can see this.
>>
>> What about this behaviour:
>>
>> ./configure    (as present -- no ELPA)
>> ./configure --enable-elpa[=some-location]   (ELPA build support)
>>
>> make elpa-update           (clone or update ELPA to some-location or default)
>> make                       (build Emacs with ELPA, break if not)
>> make DEMOTE_ELPA_ERROR=1   (build Emacs with ELPA, warning if not)
>
> Sounds OK (assuming `make` doesn't pull from elpa).

It wont need to.

I thought that this would be a pain, but actually there is a better way
to keep the two repo's in sync -- just configure the emacs git repo to
pull elpa everytime it is pulled.

Phil