From: zimoun <zimon.toutoune@gmail.com>
To: Xinglu Chen <public@yoctocell.xyz>, Andrew Tropin <andrew@trop.in>
Cc: 50077@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.)
Date: Wed, 01 Sep 2021 15:52:01 +0200 [thread overview]
Message-ID: <86mtowo132.fsf@gmail.com> (raw)
In-Reply-To: <874kb4lcvf.fsf@yoctocell.xyz>
Hi,
On Wed, 01 Sep 2021 at 14:05, Xinglu Chen <public@yoctocell.xyz> wrote:
> Cc’ing guix-devel to see what other people think before we start
> breaking people’s setups. :-)
I agree with this Andrew’s comment:
P.S. I know that there are some emacs packages in Guix already, which
doesn't use emacs-build-system, but I think we should keep that number
as low as possible and ideally to make it equal to 0 =)
<http://issues.guix.gnu.org/issue/50077#5>
If I do:
guix install emacs-next notmuch
then there is no guarantee that “M-x notmuch” will work. Because
’notmuch.el’ is byte-compiled using ’emacs-no-x’. The issue is that
some Emacs packages rely on ’emacs-minimal’, others on ’emacs-no-x’ as
input, others on other Emacs VM variant, therefore the transformation
guix build -m manifest.scm --with-input=emacs-minimal=emacs-next
will not work, as pointed by Nicolas here [1]. Well, you will tell me
that ’outputs’ does not change much the issue. :-) For sure, but IMHO
having Emacs packages using ’emacs-build-system’ eases the write of
generic transformation. Well, there is enough corner cases with Emacs
packages using ’emacs-build-system’ which rewriting their ’#:emacs’
argument. Other speaking about Emacs packages using other build
systems.
Another point is, if I want to build ’notmuch’ but I am not an Emacs
user, then:
guix environment notmuch
will download ’emacs-no-x’ for nothing. When my network is poor, I am
unhappy. Although, it is already the case. :-) Well, this is something
known, see:
<https://git.savannah.gnu.org/cgit/guix.git/tree/TODO#n37>
I am not convinced that several outputs help. And generally speaking,
personally, I tend to prefer package inherit over several outputs.
Matter of taste I guess. :-)
Without speaking about cross-compilation. ;-)
From my point of view, I would split the package ’notmuch’ and propagate
this new ’notmuch’ package with a new ’emacs-notmuch’ (if ’notmuch.el’
requires it). Well, from my point of view, it would be how to improve
the situation. :-)
All the best,
simon
1: <http://issues.guix.gnu.org/41732#14>
next prev parent reply other threads:[~2021-09-01 13:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 14:10 [bug#50077] [PATCH 0/3] Various improvements to Notmuch Xinglu Chen
2021-08-16 14:12 ` [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output Xinglu Chen
[not found] ` <87o89owoi0.fsf@trop.in>
2021-08-28 10:34 ` Xinglu Chen
2021-08-30 7:14 ` Andrew Tropin
2021-08-30 13:33 ` [bug#50077] Separate ‘emacs’ output vs separate ‘emacs-’ package (was Re: [bug#50077] [PATCH 1/3] gnu: notmuch: Add separate 'emacs' output.) Xinglu Chen
2021-09-01 9:50 ` Andrew Tropin
2021-09-01 12:05 ` Xinglu Chen
2021-09-01 12:48 ` Liliana Marie Prikler
2021-09-01 23:25 ` Carlo Zancanaro
2021-09-03 16:14 ` Xinglu Chen
2021-09-01 13:52 ` zimoun [this message]
2021-08-16 14:12 ` [bug#50077] [PATCH 2/3] gnu: notmuch: Build Info manual Xinglu Chen
2021-08-16 14:12 ` [bug#50077] [PATCH 3/3] gnu: notmuch: Use 'cc-for-target' instead of hardcoding 'gcc' Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 0/3] Improvements to Notmuch Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 1/3] gnu: notmuch: Build Texinfo manual Xinglu Chen
2021-09-04 9:41 ` [bug#50077] [PATCH v2 2/3] gnu: notmuch: Make cross-compilable Xinglu Chen
2021-09-04 9:42 ` [bug#50077] [PATCH v2 3/3] gnu: Add emacs-notmuch Xinglu Chen
2021-09-14 7:22 ` Andrew Tropin
2021-09-14 15:29 ` Xinglu Chen
2021-09-14 15:35 ` zimoun
2021-09-14 19:20 ` Xinglu Chen
2021-09-14 7:05 ` bug#50077: [PATCH v2 0/3] Improvements to Notmuch Nicolas Goaziou
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=86mtowo132.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=50077@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=public@yoctocell.xyz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.