[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Improving GNU ELPA
|
From: |
Clément Pit-Claudel |
|
Subject: |
Re: Improving GNU ELPA |
|
Date: |
Tue, 11 Jul 2017 21:26:32 -0400 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 2017-07-11 12:04, Stefan Monnier wrote:
> - we don't want to fetch from non-GNU servers, so we need the maintainer
> to push to elpa.git explicitly.
Not really (I think you hint at this a bit later): if the FSF hosts a gitlab
instance, or any sort of (multi-repo) git hosting, then developers could just
mirror their repos to that instance.
And in fact we already have this. ELPA could work just like MELPA, but
restricting the package source to Savannah. Then publishing to ELPA would be
just like MELPA, except for having to mirror to Savannah from time to time.
Clément.
- Re: Adding advisory notification for non-ELPA package.el downloads, (continued)
Re: Adding advisory notification for non-ELPA package.el downloads, Joost Kremers, 2017/07/10
Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads), Stefan Monnier, 2017/07/11
Re: Improving GNU ELPA, Etienne Prud’homme, 2017/07/13
Re: Improving GNU ELPA, Phillip Lord, 2017/07/13
Re: Improving GNU ELPA (was: Adding advisory notification for non-ELPA package.el downloads), Jonas Bernoulli, 2017/07/16
Re: Improving GNU ELPA, Stefan Monnier, 2017/07/16
Re: Improving GNU ELPA, Jonas Bernoulli, 2017/07/16
Re: Improving GNU ELPA, Phillip Lord, 2017/07/17