| 1 |
On Thu, Oct 06, 2005 at 01:13:53AM +0100, Ciaran McCreesh wrote: |
| 2 |
> On Wed, 5 Oct 2005 18:40:46 -0500 Brian Harring <ferringb@g.o> |
| 3 |
> wrote: |
| 4 |
> | > It does in some places, it doesn't in others. It especially doesn't |
| 5 |
> | > for things that aren't normally found via PATH. It's a hell of a |
| 6 |
> | > mess. |
| 7 |
> | |
| 8 |
> | Examples? |
| 9 |
> |
| 10 |
> Of stuff in PATH? /bin/sh is assumed throughout to be a Bourne |
| 11 |
> compatible shell (and SHELL and CONFIG_SHELL aren't universally |
| 12 |
> honoured). uname, hostname and sed are called with hard paths (with |
| 13 |
> various fallbacks) in several early on stages. Of stuff not in path? |
| 14 |
> There's no standard and widely used way of digging up where libexec |
| 15 |
> tools are. |
| 16 |
What's being raised here is issues with making ebuilds handle prefix |
| 17 |
_perfectly_. Where are the portage issues, so that people can |
| 18 |
actually jump in and start testing out actual solutions, rather then |
| 19 |
conjecturing about what may or may not break? |
| 20 |
~harring |
Archives