| 1 |
On Thu, Oct 06, 2005 at 12:38:35AM +0100, Ciaran McCreesh wrote: |
| 2 |
> On Wed, 5 Oct 2005 18:22:37 -0500 Brian Harring <ferringb@g.o> |
| 3 |
> wrote: |
| 4 |
> | On Thu, Oct 06, 2005 at 12:14:30AM +0100, Ciaran McCreesh wrote: |
| 5 |
> | > On Wed, 5 Oct 2005 18:00:12 -0500 Brian Harring |
| 6 |
> | > <ferringb@g.o> |
| 7 |
> | > wrote: |
| 8 |
> | > | Beyond that, there is the shebang issue which can be addresses |
| 9 |
> | > | via a combination of automated scans/fixes, and fixing bugs as |
| 10 |
> | > | it's hit. Hardcoded vars in scripts for the path to a binary are |
| 11 |
> | > | an issue also, although again, scans can be done to at least |
| 12 |
> | > | check for it. |
| 13 |
> | > |
| 14 |
> | > This one's a far bigger issue than might be initially obvious. It |
| 15 |
> | > would involve rewriting a whole load of autotools innards... |
| 16 |
> | |
| 17 |
> | Clarify. My knowledge of autotool innards is that it relies on $PATH |
| 18 |
> | for lookup of the tools it uses. |
| 19 |
> |
| 20 |
> It does in some places, it doesn't in others. It especially doesn't for |
| 21 |
> things that aren't normally found via PATH. It's a hell of a mess. |
| 22 |
Examples? |
| 23 |
~harring |
Archives