Re: feature/integrated-elpa 4f6df43 15/23: README added

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: John Wiegley <address@hidden>,  address@hidden,  address@hidden
> Date: Tue, 18 Oct 2016 14:01:52 +0100
> 
> >> PL> I think it's decision time. I am happy to carry on a little further 
> >> with
> >> PL> the package.el based approach that I have outlined, fixing the one
> >> PL> significant issue with it and then I will stop. If you don't want to go
> >> PL> this way, that's fine.
> >
> > Sorry, I don't understand the kind of decision that is being
> > requested.  I understand that one alternative is that you "carry on a
> > little further" with your approach, although I'm vague about the
> > details of that, or what is your goal.
> 
> Complete the code that I have started. Three goals:
> 
>  - Use package.el to build (compile, generate autoloads) packages in
>    during the build
>  - Use package.el to initialize and load these during startup
>  - Support testing of these packages during build.
> 
> With a secondary aim of:
> 
>  - Enable a built emacs to build and test all packages in ELPA whether
>    they are core/tarball or not.

Can this be done while keeping the current structure under lisp/
intact and putting packages from ELPA under lisp/ ?  If yes, I think
this is what we all want.