[neomutt-devel] mutt vs neomutt
Julian Andres Klode
jak at jak-linux.org
Sun Jun 25 01:50:49 CEST 2017
On Sun, Jun 25, 2017 at 12:07:27AM +0200, Sven Guckes wrote:
> i see that all the debian packages
> of mutt are now all neomutt.
> install mutt - receive neomutt.
> this sounds all pretty confusing.
It's not really confusing. Debian's mutt package was always heavily
patched. Most of these changes were forwarded to and merged into neomutt,
so keeping a separate line of downstream patches would just be a lot
of duplicated effort, when NeoMutt already collects patches against
mutt for you :)
NeoMutt effectively replaced "pure" mutt in 1.6.1-1, but it was
shipped as a patch to be applied on top of the mutt sources until
today, because that's no longer feasible, so Debian's mutt package
is now directly built from a neomutt tarball, so the versioned
was changed to reflect that today with 1.8.3+neomutt20170609-1.
> so.. what are the plans here?
> will there be only one package?
> who will do the support? etc
> will there be a "native" mutt package again?
There is one mutt package, shipping neomutt. It is maintained
by the pkg-mutt maintainers as before. There are currently no
plans to ship a mutt without neomutt.
I hope that makes things a bit clearer.
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
More information about the neomutt-devel