New comment by emacsomancer on void-packages repository https://github.com/void-linux/void-packages/pull/32396#issuecomment-894792671 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. 2. I think it would be far better for a merged package to be called `mu4e` rather than `mu` (since the former is (a) user-facing piece; (b) what people will general be searching for; (c) long enough to avoid name-collisions).