Github messages for voidlinux
 help / color / mirror / Atom feed
From: emacsomancer <emacsomancer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mu: update to 1.6.2
Date: Sun, 08 Aug 2021 15:42:41 +0200	[thread overview]
Message-ID: <20210808134241.FPSBeDm5eWm061p_DPFbHIzAnVoWb5WZ-K2aYZdPkFM@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: 914 bytes --]

New comment by emacsomancer on void-packages repository

https://github.com/void-linux/void-packages/pull/32396#issuecomment-894799818

Comment:
> `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.

So then could all of the `if [ ! "$CROSS_BUILD" ]` conditionals just be removed?

What about `emacs` as a dependency?

> > 2. I think it would be far better for a merged package to be called `mu4e` rather than `mu`....

> 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`.

I can't really think of a use for `mu` without `mu4e`, but in theory I suppose someone could just have `mu` installed.

But:

````
$ xbps-query -Rs mu | wc -l
1080

$ xbps-query -Rs mu4e | wc -l
1
````

  parent reply	other threads:[~2021-08-08 13:42 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
2021-08-08 13:42 ` emacsomancer [this message]
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=20210808134241.FPSBeDm5eWm061p_DPFbHIzAnVoWb5WZ-K2aYZdPkFM@z \
    --to=emacsomancer@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).