[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA policy
From: |
Óscar Fuentes |
Subject: |
Re: ELPA policy |
Date: |
Sun, 08 Nov 2015 19:26:20 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
Eli Zaretskii <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.
>
> ELPA requires Internet access if you are building from the repository.
>
> My greatest fears are that packages that move from core to ELPA will
> get much less attention from the core maintenance team, which will
> eventually degrade their quality.
Org-mode, for instance, gets regular bug fix releases on GNU ELPA while
it stagnates on core. I would venture that the contribution from the
"core maintenance team" to org-mode amounts to a negative effect,
causing more hassle than it saves.
For projects with their own development team and VCS repository, having
the project copied into the Emacs core VCS makes no sense, moreover when
they have to support multiple Emacs releases.
- Re: ELPA policy, (continued)
- Re: ELPA policy, Richard Stallman, 2015/11/06
- Re: ELPA policy, John Wiegley, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Wolfgang Jenkner, 2015/11/08
- Re: ELPA policy, Eli Zaretskii, 2015/11/08
- Re: ELPA policy, Wolfgang Jenkner, 2015/11/08
- Re: ELPA policy,
Óscar Fuentes <=
- 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, 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