[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: Mon, 03 Oct 2016 13:33:53 +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> Sure, but it cannot change the fact that ELPA and Emacs core have
> PL> different organisations because Emacs has a unified (or monolithic
> PL> depending on your POV) directory structure, while ELPA has a per-package
> PL> structure.
> I understand that ELPA has per-package structure, but there's no requirement
> for this to be a physical mapping.  As long as we know which files within
> EMACS corresponding to the package files within the EPLA package, this is
> sufficient.
> So, if the mapping of EPLA-tree to Emacs-tree is not obvious by convention, we
> could introduce a file to provide that mapping. It's doesn't need to be
> either-or, simply because of current physical mappings.
>     ELPA/foo/foo.el
>     ELPA/foo/doc/foo.doc
> could virtually map to:
>     EMACS/lisp/foo.el
>     EMACS/doc/foo.doc
> by convention. Or more complex scenarios by a mapping file. Since we have a
> full programming language at our behest, there is no limit to our
> organizational capabilities. :)

Yes, sure. But as Emacs is already capable of building and loading
packages in package.el format, why not use that?


reply via email to

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