unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 24433@debbugs.gnu.org
Subject: bug#24433: fish needs to have bc in propagated-inputs
Date: Wed, 14 Sep 2016 09:57:42 -0400	[thread overview]
Message-ID: <CAJ=RwfbZaR+kSi4eH5Gs-dnTJ4SPhzQS4n9O2NoekC0d2ZuWaQ@mail.gmail.com> (raw)
In-Reply-To: <cu7d1k6zx32.fsf@systemreboot.net>

On Wed, Sep 14, 2016 at 4:48 AM, Arun Isaac <arunisaac@systemreboot.net> wrote:
>
> 'fish' needs 'bc' as a propagated input. I have noticed runtime errors
> due to absence of bc. It's also mentioned here:
>
> https://github.com/fish-shell/fish-shell#runtime-dependencies
>
> Quoting the relevant paragraph:
>
> "fish requires a number of utilities to operate, which should be present
> on any Unix, GNU/Linux or OS X system. These include (but are not
> limited to) hostname, grep, awk, sed, which, and getopt. fish also
> requires the bc program."

A runtime dependency does *not* mean that an input should be
propagated.  Propagation is a solution of last resort.

Instead, try finding the places where 'bc' is referenced in the fish
source and replace it with the absolute path to the binary.

Thanks,

- Dave

  reply	other threads:[~2016-09-14 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  8:48 bug#24433: fish needs to have bc in propagated-inputs Arun Isaac
2016-09-14 13:57 ` Thompson, David [this message]
2016-09-15  6:23   ` Arun Isaac
2016-09-16 21:00   ` bug#24433: Arun Isaac
2016-09-16 21:00     ` bug#24433: [PATCH] gnu: fish: Add input bc Arun Isaac
2016-09-25 22:07       ` Arun Isaac
2016-10-04  9:27       ` Ludovic Courtès
2016-10-04 14:19         ` 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

  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='CAJ=RwfbZaR+kSi4eH5Gs-dnTJ4SPhzQS4n9O2NoekC0d2ZuWaQ@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=24433@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).