[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EWW To Elpa? Re: Having a custom merge process
|
From: |
Artur Malabarba |
|
Subject: |
Re: EWW To Elpa? Re: Having a custom merge process |
|
Date: |
Sat, 26 Dec 2015 18:40:14 +0000 |
On 26 Dec 2015 3:00 pm, "raman" <address@hidden> wrote:
>
> Given that EWW is a relatively stand-alone package, should it also be
> available via elpa -- in addition to being bundled?
I think it can be made available as a :core elpa package (this means it would still be developed in Emacs core, and automatically made available in elpa by the scripts).
As far as eww is concerned, we would only have to add a Package-Requires header and bump the version number once in a while.
- Re: Having a custom merge process, (continued)
- Re: Having a custom merge process, Eli Zaretskii, 2015/12/26
- Re: Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch), Eli Zaretskii, 2015/12/26
- EWW To Elpa? Re: Having a custom merge process, raman, 2015/12/26
- Re: EWW To Elpa? Re: Having a custom merge process, Lars Ingebrigtsen, 2015/12/26
- Re: EWW To Elpa? Re: Having a custom merge process, Artur Malabarba, 2015/12/26
- Re: EWW To Elpa? Re: Having a custom merge process, John Wiegley, 2015/12/28
- Re: EWW To Elpa? Re: Having a custom merge process,
Artur Malabarba <=
- Re: EWW To Elpa? Re: Having a custom merge process, raman, 2015/12/27
- Re: Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch), Richard Stallman, 2015/12/26
- Re: Having a custom merge process (was: EWW bugs should be fixed on emacs-25 branch), Eli Zaretskii, 2015/12/26
Re: EWW bugs should be fixed on emacs-25 branch, Lars Ingebrigtsen, 2015/12/25