From: Joshua Pollak <pardsbane@offthehill.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Sandbox suggestion
Date: Tue, 11 Dec 2001 14:21:12 -0500 [thread overview]
Message-ID: <E16DsTc-00065A-00@granger.mail.mindspring.net> (raw)
In-Reply-To: <1008095033.1061.0.camel@willow.theleaf.office>
On Tuesday 11 December 2001 1:23, you wrote:
> most scripts refer to bash like this
>
> #!/bin/bash
>
> putting another one in the path doesn't work around this at all
Perhaps gentoo policy could be to make ebuilds reference:
#!/bin/ebuild-bash
which by default would be a sym-link to bash, but on a sandbox system would
have the dynamic bash in place?
I don't know how much of an issue using the wrong shell is, I don't know how
often people will encounter problems, but I do know that when bash got
version skewed (or something) on my Debian system, it was a nightmare.
next prev parent reply other threads:[~2001-12-11 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 4:51 [gentoo-dev] Sandbox suggestion Joshua Pollak
2001-12-11 9:05 ` Geert Bevin
2001-12-11 16:22 ` Joshua Pollak
2001-12-11 18:04 ` Zach Forrest
2001-12-11 18:23 ` Geert Bevin
2001-12-11 19:21 ` Joshua Pollak [this message]
2001-12-11 19:25 ` Geert Bevin
2001-12-11 19:40 ` Zach Forrest
2001-12-11 20:04 ` Daniel Robbins
2001-12-11 20:16 ` Zach Forrest
2001-12-11 20:17 ` Daniel Robbins
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=E16DsTc-00065A-00@granger.mail.mindspring.net \
--to=pardsbane@offthehill.org \
--cc=gentoo-dev@gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox