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

[phillip.lord@russet.org.uk (Phillip Lord)]

phillip.lord@russet.org.uk (Phillip Lord) writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I've also got working code that takes an ELPA package and copies it into
>>> the core build.  It's quite simple to do actually, the documentation
>>> needs improving and to plump in some configure options.  It would raise
>>> the possibility of having a "Emacs minimal" core distribution (i.e. with
>>> no "elpa" packages).  Interested?
>>
>> I think we need that, yes (e.g. we really should bundle Company with
>> Emacs while we want to keep it in elpa.git).  But it's for Eli to decide
>> if and how he wants such a thing.
>
> I've pushed this to:
>
> feature/core-elpa-by-copy
>
> Currently, it's in as a feature
>
> ./configure --enable-elpa
> ./configure --enable-elpa=where-to-find-or-clone-elpa
>
> Main features:
>
>  - Works with externals or non-external packages.
>  - Versions are specified by git SHA, so a version build will be
>    repeatable.
>  - Both code and tests are supported
>  - It's customizable by package authors on ELPA.
>  - Doesn't use package.el (I think this is an anti-feature, but tried
>    that before and no one liked it)
>  - It requires network access only if ELPA is not available locally, or if
>    the Makefile which describes versions is updated
>  - Works with make -j in which case it does a git clone which the C is building
>
> None Features: 
>  - Currently, only works with a single git repo (i.e. ELPA) which is
>    hard coded.
>  - Doesn't support documentation or info
>
> To be done:
>  - Give it prettier output
>  - Clean ups.


Wondering whether anyone had time to give me feedback on this. It
provides a mechanism to have ELPA packages bundle with core Emacs.

Phil