mutt 1.6.0 fails to apply the ignore-thread patch about homebrew-core HOT 10 CLOSED

I just came to report the same thing. I checked, and I don't yet see an updated ignore-thread patch for mutt 1.6: https://dev.mutt.org/trac/wiki/PatchList. I know the mutt patches have long been a sore-spot for Homebrew. Would it make sense to pull the patch until it's updated?

from homebrew-core.

Would it make sense to pull the patch until it's updated?

Yup (and even after it's updated, unfortunately).

from homebrew-core.

Maybe there's need for a mutt-kz formula,
https://github.com/karelzak/mutt-kz.

On 5 April 2016 at 14:12, Mike McQuaid [email protected] wrote:

Would it make sense to pull the patch until it's updated?

Yup (and even after it's updated, unfortunately).

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#74 (comment)

from homebrew-core.

Yup (and even after it's updated, unfortunately).

To clarify, does this mean you want to pull this patch forever? If so, do you want also to pull all patches from mutt?

I understand if that's how you want to go, but it will almost certainly lead to a large number of people giving up the mainline version of mutt. Maybe that's for the best, but I think it would be a shame. Unfortunately, mutt's development style just doesn't fit Homebrew's preferred model. That is, upstream is not going to change much, I don't think.

from homebrew-core.

There just needs to be a mutt tap (not a HB official one, of course).

from homebrew-core.

A few people listed theirs in Homebrew/legacy-homebrew#43647; I don't think any are widely used though.

from homebrew-core.

For historical purposes, there was also discussion in several earlier threads. Here's a few I recall that may have useful information or ideas:

1. Homebrew/legacy-homebrew#20516
2. Homebrew/legacy-homebrew#20588
3. Homebrew/legacy-homebrew#20677

from homebrew-core.

#80

from homebrew-core.

(guy who submitted the change to upgrade to 1.6.0 here, and I just use and get used to only mutt-core to avoid actually issues with such patches and keep up with the latest versions).

Personally, if there are patches available and users willing to use them because they think they are more useful than upstream core set of features, there are no reasons not to add them in the future if they work. Now, I don't think that those patches should be an obstacle for upgrades, or we increase the risk to be stuck with old versions of mutt forever, because not only would this package rely on the availability of the core maintainer of mutt, but also on the person who is generating those alpha patches. Integrating things directly to upstream may make more sense, now I am sure that there are valid reasons why mutt core code is being conservative and does not integrate them.

from homebrew-core.

Integrating things directly to upstream may make more sense, now I am sure that there are valid reasons why mutt core code is being conservative and does not integrate them.

Agreed 👍

from homebrew-core.