From: Alex Kost <alezost@gmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] update notmuch and python bindings
Date: Mon, 08 Aug 2016 11:20:39 +0300 [thread overview]
Message-ID: <877fbrzn6w.fsf@gmail.com> (raw)
In-Reply-To: <8737mggrr9.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Sun, 07 Aug 2016 22:04:42 +0000")
ng0 (2016-08-08 01:04 +0300) wrote:
> Troy Sankey <sankeytms@gmail.com> writes:
>
>> Quoting ng0 (2016-08-07 15:29:34)
>>> > (inputs
>>> > - `(("emacs" ,emacs)
>>> > - ("glib" ,glib)
>>> > + `(("glib" ,glib)
>>>
>>> Why is emacs removed?
>>
>> Please see the commit message :)
>>
>> Of course I could be misunderstanding something, but it does build
>> successfully. I do not normally use emacs, so I was not able to test
>> this particular change.
Commit message:
This also removes the emacs input. Quote from the notmuch NEWS file:
Drop dependency on "pkg-config emacs".
This only means that emacs is not required for notmuch to be built
successfully (it is done for those people who don't use emacs). But it
doesn't mean this dependency should be dropped. In Guix we usually
include all available features.
> Ah, sorry.
> I don't want to mix up my notmuch and the review, and I'll be occupied
> until tuesday night, so someone who does not rely on a functional
> notmuch should review if it works correctly. I find it weird that the
> input is dropped.
You are right, emacs input shouldn't be dropped. This would lead to
non-compiled elisp files (I mean
/gnu/store/...-notmuch-0.22.1/share/emacs/site-lisp/ would contain only
*.el files but not *.elc).
I would rather replace 'emacs' with 'emacs-minimal', also I think it
should be moved to 'native-inputs'; but this does not relate to this
patch (I'll commit this change separately).
--
Alex
next prev parent reply other threads:[~2016-08-08 8:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 18:55 [PATCH] update notmuch and python bindings Troy Sankey
2016-08-07 19:29 ` ng0
2016-08-07 20:40 ` Troy Sankey
2016-08-07 22:04 ` ng0
2016-08-08 8:20 ` Alex Kost [this message]
2016-08-07 22:24 ` ng0
2016-08-08 4:34 ` Troy Sankey
2016-08-08 7:05 ` ng0
2016-08-08 7:42 ` ng0
2016-08-08 13:31 ` Troy Sankey
2016-08-08 8:21 ` Alex Kost
2016-08-11 15:18 ` Alex Kost
2016-08-08 21:30 ` Leo Famulari
2016-08-08 8:35 ` Alex Kost
2016-08-08 15:07 ` Troy Sankey
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fbrzn6w.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).