[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Phillip Lord
Subject: Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added
Date: Sun, 09 Oct 2016 21:25:00 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

John Wiegley <address@hidden> writes:

>>>>>> "PL" == Phillip Lord <address@hidden> writes:
> PL> AFAICT the layout of files inside the Emacs directory is, or should be,
> PL> more or less irrelevant to the end user of Emacs. We do not need to
> PL> maintain the current directory structure, to maintain the user experience.
> I think we're getting hung up on package.el, rather than focusing on how to
> best integrate ELPA with our development process. Many people, myself
> included, don't want to see files start moving around just to suit
> package.el's conventions. We can *always* map ELPA project files to custom
> locations as needed, or even change package.el.

Yes, this is true. I am suggesting a very simple mapping -- we use the
same structure as ELPA.

> So let's get back to how we can adapt our build process to include ELPA (1) in
> the release tarball (for "ELPA tarball" packages), and (2) in our mainline
> development (for "ELPA core" packages).

Still confused about this, so let me check that I have this correct.

An ELPA tarball package would be included in the tarball.

An ELPA core package would be including in the tarball, and other
packages would be free to use it as a dependency?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]