Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added

[Phillip Lord]

Eli Zaretskii <address@hidden> writes:

>> From: address@hidden (Phillip Lord)
>> Cc: Alain Schneble <address@hidden>,  address@hidden,  address@hidden
>> Date: Sun, 09 Oct 2016 21:42:59 +0100
>> 
>> Eli Zaretskii <address@hidden> writes:
>> >> Or if you meant without pushing at all, then none of the above would be
>> >> an issue, I think.  But the logic of getting ELPA core packages into the
>> >> Emacs directory tree would be a bit different, as it would have to get
>> >> the files from the local git clone.
>> >
>> > I was hoping the modified package.el will help us get the files from
>> > the repository, either local or remote, directly into the Emacs source
>> > tree.
>> 
>> Yes, I do not know how this would be be achieved at the moment.
>
> One possibility is to have each ELPA package tell package.el where its
> files should live in the Emacs tree.  For example, each package could
> have a standard-named file with a Lisp data structure that specifies
> this.  package.el would then use this information to place each file
> where it belongs.

If we are moving files into the current directory structure, I'm not
sure we need package.el at all. It would be doing something totally
different from what it does at the moment (which is select, download,
install and initialize packages).


> We could also have a set of reasonable defaults; for example the tests
> should by default go to the directory under test/lisp/ whose name is
> identical to the lisp/ subdirectory of the Lisp files.

I think that this is essentially what ever we choose, although
personally, I would not have defaults, just a set of standards which
need to be followed.

We have some of this with ELPA already; I've already noted that there is
no standard location for test files in ELPA, and it is something I would
like to add.

Phil