From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11426] New: pps-tools bash dependency
Date: Mon, 22 Oct 2018 14:35:51 +0000 [thread overview]
Message-ID: <bug-11426-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11426
Bug ID: 11426
Summary: pps-tools bash dependency
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jan.dohl at airrays.com
CC: buildroot at uclibc.org
Target Milestone: ---
When installing the pps-tools package without installing Bash, the ppsfind
script in the package will not work. For example:
# uname -a
Linux xla 4.14.0-xla #4 SMP PREEMPT Fri Oct 19 17:56:30 CEST 2018 aarch64
GNU/Linux
# ppsfind
-sh: ppsfind: not found
# which ppsfind
/usr/bin/ppsfind
# cat /usr/bin/ppsfind | head -n 1
#!/bin/bash
Not sure what the best course of action is here, though. I think making Bash a
dependency for pps-tools is not a good idea. The ppsfind script works fine by
just replacing the shebang with /bin/sh instead. The latter is probably also a
good suggestion for the upstream repository.
Would a patch for the time being while also reporting this to the upstream be a
good idea?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-10-22 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 14:35 bugzilla at busybox.net [this message]
2018-10-22 22:39 ` [Buildroot] [Bug 11426] pps-tools bash dependency bugzilla at busybox.net
2018-11-09 15:58 ` bugzilla at busybox.net
2018-11-10 8:54 ` bugzilla at busybox.net
2018-12-03 13:04 ` bugzilla at busybox.net
2018-12-19 22:01 ` bugzilla at busybox.net
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=bug-11426-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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.
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.