[MacPorts] #52297: mutt @1.6: make it obsolete in favor of neomutt

MacPorts noreply at macports.org
Fri Sep 23 17:27:17 CEST 2016


#52297: mutt @1.6: make it obsolete in favor of neomutt
----------------------------------+--------------------------------
  Reporter:  leonardo.schenkel@…  |      Owner:  macports-tickets@…
      Type:  enhancement          |     Status:  closed
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:  2.3.4
Resolution:  fixed                |   Keywords:
      Port:  mutt                 |
----------------------------------+--------------------------------

Comment (by vkuznet@…):

 I don't understand why you asked to make mutt obsolete. Why not to make
 neomutt as individual project. Sometimes we don't want to stay on bleeding
 edge. I want to try it but I don't want to overwrite existing mutt. What
 if my settings in mutt will not work in neomutt? I can raise many
 questions. Also, I want to try out next stable version 1.7 separately. I
 think making neomutt overwrite mutt itself is wrong approach since they
 can nicely coexists and give users flexibility to choose, try out and
 experiment with both.

-- 
Ticket URL: <https://trac.macports.org/ticket/52297#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list