On Thu, Oct 06, 2005 at 12:14:30AM +0100, Ciaran McCreesh wrote: > On Wed, 5 Oct 2005 18:00:12 -0500 Brian Harring <[EMAIL PROTECTED]> > wrote: > | Beyond that, there is the shebang issue which can be addresses via a > | combination of automated scans/fixes, and fixing bugs as it's hit. > | Hardcoded vars in scripts for the path to a binary are an issue also, > | although again, scans can be done to at least check for it. > > This one's a far bigger issue than might be initially obvious. It would > involve rewriting a whole load of autotools innards... Clarify. My knowledge of autotool innards is that it relies on $PATH for lookup of the tools it uses.
> | Leaves mangling the build process so that the build framework of the > | package uses the prefix offset files, rather then / . For c/c++ > | source, usual trick from fink afaik involves a mangling of cflags > | with -I tacked in. Kinda ugly, although I'd expect there is a better > | route. > > Again, autoconf tinkering. Statement above is from digging through generated configure script. ~harring
pgp3yrxiLkcfh.pgp
Description: PGP signature
