[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#889056: [update] Re: Bug#889056: replace apache-mode.el with elpa package



On Wed, Jul 04, 2018 at 07:08:26AM -0300, David Bremner wrote:
> Nicholas D Steeves <nsteeves@gmail.com> writes:
> 
> > https://github.com/martenjj/apachemode is also by Jonathan Marten
> >   - Notes that it merges the features of three forks back into the
> >     original.
> > https://github.com/emacs-php/apache-mode/ is a fork by Karl Chen, and
> > I wonder if it would be as smooth of a transition.  The fork would
> > be new to Debian...
> >
> > At any rate, the RFC: Do we want the version by the original author,
> > which merges the features from three forks, or do we want the version
> > on MELPA.  If necessary, I'd be happy to contact Jonathan Marten to
> > ask him if he would be willing to push his package to MELPA.
> 
> Being on melpa is not a prerequisite for being in Debian, as long as the
> upstream seems maintained.
> 
> I don't use apache so I can't really comment on the merits of the two
> modes. I do notice that the emacs-php one has tags, and is more recently
> active (2017 vs 2016). So I guess go for that one if you don't find a
> better way to break the tie.

https://github.com/martenjj/apachemode
 + original author
 + merges features from three forks
 + has a LICENSE file
 + has an issue tracker
 + easier to extend by patching keyword lists--CSVs

https://github.com/emacs-php/apache-mode/
 + more up-to-date
 + tags releases
 + could also become the version people come to expect, because it's
   on MELPA
 - no description or documentation beyond the short description
   and a code snippet for how to auto-enable the mode.

Ftpmasters would prefer martenjj's copy, because it has a LICENSE
file.  I've filed an upstream issue to investigate if martenjj would be
willing to tag a stable release, and reveal plans for future updates:
  https://github.com/martenjj/apachemode/issues/1

and have emailed Karl Chen (CCed our list) to address the issues on
his copy.

Cheers,
Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: