New comment by sgn on void-packages repository https://github.com/void-linux/void-packages/pull/32396#issuecomment-894796698 Comment: > I don't have any particular opinion one way or other (I "inherited" the package in this split fashion.) > > Two thoughts: > > 1. I'm not sure what the implications of merging the two might be for arm/crossbuilds. `mu4e` was disabled for cross build because `emacs` wasn't available there. However, `mu4e` is simply text files, and anyone that have it should have emacs installed already. I'm in favor of merging because someone who wants to use mu4e on (let's say) aarch64, can just build emacs themselves and install `mu` (or `mu4e`) and use it, instead of rebuild `mu`. > 2. I think it would be far better for a merged package to be called `mu4e` rather than `mu` (since the former is (a) the name of the user-facing piece; (b) what people will general be searching for; (c) long enough to avoid name-collisions). I have no opinion, either way. One thing: someone who only have mu installed (who are they anyway?) won't see the upgrade from `mu` to `mu4e`.