Matthew Sachs wrote: []
This applies to many more scripts on the system than just gcc_select, and I don't believe that any of them set their own PATH. gcc_select
Looking at some of the examples, one sees indeed very different levels of careful programming. Some of the scripts go to great lengths to always use the complete path like /bin/rm etc, others are pretty sloppy. Some are at the limit of the ridiculous like apachectl which uses "which" in a sh script, with rather unpredictable outcome.
And one should add that the fact that we need to run gcc_select from fink at all is caused by a bug in the concept of gcc_select. It fiddles with things that other system tools consider immutable.
isn't particularly vital or dangerous -- if it gets things wrong, worst case you need to reinstall XCode.
I would consider this rather serious, in particular when it can happen out of the blue sky, just because some library is temporarily not what or where it is supposed to be.
-- Martin ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
