Summary: | Ebuilds fail when /bin/sh-Link isn't set to bash | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Heinz Striebeck <deppdepp> |
Component: | Core - Interface (emerge) | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Heinz Striebeck
2005-06-12 15:23:02 UTC
You hand-edited a very important sym link that was installed by a system package and then things broke. That's pretty firmly in the "you break it, you buy it" category. It's your system, so you can do whatever you want to it, but it's not a bug in Gentoo. Wrong! Designating #!/bin/sh as interpreter while using bash elements for sh scripts, breaks with almost all Unix-world standards. Using bash features while calling /bin/sh IS a bug, one that spreads like cancer. Result: b0orken you didnt prove that dash or tcsh are the ones to blame here autoconf is designed to be written in portable sh so i'd be highly doubtful that it's the one to blame here ... much more likely the shell you're dropping in place of /bin/sh is the thing that's broken do some research before you start complaining loudly |