[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELPA policy
From: |
John Wiegley |
Subject: |
Re: ELPA policy |
Date: |
Tue, 10 Nov 2015 12:24:15 -0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) |
>>>>> David Engster <address@hidden> writes:
> the main question is whether something provides infrastructure for other
> packages to use.
Sounds like a good sentence for an ELPA policy. :)
> It is still not clear to me what exactly is gained by moving core packages
> to ELPA.
Agility. What is appropriate. Knowing when a thing goes into core, and when in
ELPA.
Org is an application, it's not infrastructure; the same with Gnus. *Parts* of
Gnus might rightly be considered infrastructure, but the whole of Gnus just
doesn't belong there. Parts of CEDET probably do belong in Emacs core, but as
an application, I don't think the whole of it does.
Since we don't have an agreed upon basis by which to draw such lines, we're
both talking about what we feel is right. Let's agree to revisit after having
the ELPA discussion.
John
- Re: ELPA policy, (continued)
- Re: ELPA policy, Dmitry Gutov, 2015/11/10
- Re: ELPA policy, David Engster, 2015/11/10
- Re: ELPA policy, John Wiegley, 2015/11/10
- Re: ELPA policy, David Engster, 2015/11/10
- Re: ELPA policy, John Wiegley, 2015/11/10
- Re: ELPA policy, David Engster, 2015/11/10
- Re: ELPA policy, John Wiegley, 2015/11/10
- Re: ELPA policy, David Engster, 2015/11/10
- Re: ELPA policy,
John Wiegley <=
- Re: ELPA policy, Stephen Leake, 2015/11/10
- Re: ELPA policy, John Wiegley, 2015/11/10
- RE: ELPA policy, Drew Adams, 2015/11/10
- Re: ELPA policy, John Wiegley, 2015/11/10
- Re: ELPA policy, Stephen Leake, 2015/11/11
- Re: ELPA policy, Filipp Gunbin, 2015/11/11
- Re: ELPA policy, Stephen Leake, 2015/11/11
- Re: ELPA policy, Filipp Gunbin, 2015/11/12
- Re: ELPA policy, John Wiegley, 2015/11/12
- Re: ELPA policy, Filipp Gunbin, 2015/11/12