From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mu: update to 1.6.2
Date: Sun, 08 Aug 2021 15:18:49 +0200 [thread overview]
Message-ID: <20210808131849.VKWew_Sd_wPeXdnFV4x_TCi_Vsc8iAvC7C2IKJRlNbU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32396@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
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`.
next prev parent reply other threads:[~2021-08-08 13:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 16:18 [PR PATCH] " emacsomancer
2021-08-08 3:52 ` sgn
2021-08-08 12:47 ` emacsomancer
2021-08-08 12:48 ` emacsomancer
2021-08-08 13:18 ` sgn [this message]
2021-08-08 13:42 ` emacsomancer
2021-08-08 16:03 ` sgn
2021-08-08 16:34 ` emacsomancer
2021-08-08 16:34 ` emacsomancer
2021-08-08 16:36 ` emacsomancer
2021-08-08 17:25 ` [PR PATCH] [Updated] " emacsomancer
2021-08-12 0:47 ` emacsomancer
2021-08-12 21:22 ` emacsomancer
2021-08-12 21:26 ` emacsomancer
2021-08-12 21:31 ` [PR PATCH] [Updated] " emacsomancer
2021-08-12 21:58 ` emacsomancer
2021-08-12 22:02 ` emacsomancer
2021-08-12 22:03 ` emacsomancer
2021-08-13 0:48 ` [PR PATCH] [Updated] mu: update to 1.6.3 & combine mu and mu4e packages emacsomancer
2021-08-13 2:07 ` [PR REVIEW] " sgn
2021-08-13 2:07 ` sgn
2021-08-13 2:29 ` [PR PATCH] [Updated] " emacsomancer
2021-08-13 2:30 ` [PR REVIEW] " emacsomancer
2021-08-13 2:30 ` emacsomancer
2021-08-14 13:23 ` [PR PATCH] [Merged]: " sgn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210808131849.VKWew_Sd_wPeXdnFV4x_TCi_Vsc8iAvC7C2IKJRlNbU@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).