From: Arun Isaac <arunisaac@systemreboot.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 28000@debbugs.gnu.org
Subject: [bug#28000] [PATCH] gnu: octave: Build with texinfo.
Date: Tue, 26 Sep 2017 18:53:06 +0530 [thread overview]
Message-ID: <4f4688dd.AEEARAgPOysAAAAAAAAAAAPwTpIAAAACwQwAAAAAAAW9WABZylTD@mailjet.com> (raw)
In-Reply-To: <87k22fauwn.fsf@fastmail.com>
Indeed, I was waiting for a response to this patch, and am seeing your
reply only now, after almost 2 months! It looks like I'm having trouble
with my DNS configuration. :-(
>> texinfo is required for the built-in documentation.
>>
>> * gnu/packages/maths.scm (octave)[inputs]: Add texinfo.
>> [native-inputs]: Remove texinfo.
>
>If I read this right, Octave references texinfo at runtime, so it's
>moved to inputs for correctness? The commit message is a bit confusing,
>since it already has texinfo available :-)
Currently, there is a comment above the octave package definition saying
that users should install texinfo manually in their profile. My patch
allows the user to not have to do that. This is the meaning I was trying
to convey with the commit message. What other commit message would you
suggest?
next prev parent reply other threads:[~2017-09-26 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 10:43 [bug#28000] [PATCH] gnu: octave: Build with texinfo Arun Isaac
2017-08-07 22:13 ` Marius Bakke
2017-09-26 13:23 ` Arun Isaac [this message]
2017-08-07 22:18 ` [bug#28000] [Mail Delivery System] Undelivered Mail Returned to Sender Marius Bakke
2017-09-30 9:25 ` [bug#28000] [PATCH] gnu: octave: Reference makeinfo with absolute path Arun Isaac
2017-10-04 14:37 ` Ludovic Courtès
2017-10-05 22:09 ` bug#28000: " Arun Isaac
[not found] <ddec1ecd.AEEARAgPOywAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZylTD@mailjet.com>
2017-09-27 21:14 ` [bug#28000] [PATCH] gnu: octave: Build with texinfo Marius Bakke
2017-09-29 14:55 ` Arun Isaac
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=4f4688dd.AEEARAgPOysAAAAAAAAAAAPwTpIAAAACwQwAAAAAAAW9WABZylTD@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=28000@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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.