[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA policy
From: |
Artur Malabarba |
Subject: |
Re: ELPA policy |
Date: |
Sun, 08 Nov 2015 19:55:49 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
John Wiegley <address@hidden> writes:
> If that's the case, it changes my thoughts on what needs to be in core, and
> what should be in ELPA. Until now I was thinking ELPA required Internet
> access; but if there are parts of ELPA that "come in the box", then I'd like
> to see more packages there.
I think we ought to clarify what we're talking about here.
- There are packages that are offered only on Elpa. For these you need
an internet connection and you need to `M-x package-install' them.
- There are packages that are offered both on Elpa and Emacs. These
are just like any other core package (no connection and no
package-install necessary).
The difference is that users can get access to new versions from Elpa
without having to wait for the next Emacs release. The disadvantage
here is code duplication, as someone needs to make sure that any bug
fixes applied on the Emacs side also get applied on the Elpa side (and
vice versa).
Current examples of this are seq.el and let-alist.
- Then there's a third option. I only found this out recently while
browsing the `externals-list' file on Elpa, and it was apparently
implemented by Fabián in September.
You can configure Elpa to (while building) copy the most recent
version of an packages from the Emacs repository. IIUC, this would
have the same effect as the previous option, except no code
duplication. The thing is: no packages seem to be using this, and it's
only documented in the comments of that file (though I've verified
that there's indeed code to implement this).
Fabián, is this feature complete?
- Re: ELPA policy, (continued)
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Artur Malabarba, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Richard Stallman, 2015/11/08
- Re: ELPA policy, Dmitry Gutov, 2015/11/08
- Re: ELPA policy, Yuri Khan, 2015/11/08
- Re: ELPA policy,
Artur Malabarba <=
- Re: ELPA policy, Stephen Leake, 2015/11/09
- Re: ELPA policy, David Kastrup, 2015/11/05
Re: Proposed new core library: pl.el, Artur Malabarba, 2015/11/05
Re: Proposed new core library: pl.el, Ted Zlatanov, 2015/11/05
- Re: Proposed new core library: pl.el, Artur Malabarba, 2015/11/05
- Re: Proposed new core library: pl.el, Ted Zlatanov, 2015/11/06
- Re: Proposed new core library: pl.el, Ted Zlatanov, 2015/11/08
- Re: Proposed new core library: pl.el, Artur Malabarba, 2015/11/08
- Re: Proposed new core library: pl.el, John Wiegley, 2015/11/09
- Re: Proposed new core library: pl.el, Artur Malabarba, 2015/11/09