On Jun 4, 2007, at 3:14 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
I took this snippet from another project's configure.ac, I think it's a common and sensible way of handling Fink and DarwinPorts. As you have said before, the Gem build system aims to build Gem using what is installed on that machine. This would definitely help that process, people wouldn't have to know how to setup their environment in order for the Gem build to use Fink and/or DarwinPorts.
i thought the paths were found fine when running the configure by hand. i thought this problem only occurs with autobuild (e.g. cron- triggered) systems?
nevertheless, i will investigate...
If a person has set up their PATH in their environment to use Fink/ DarwinPorts, then Gem's ./configure will use it, just like any other program that inherits env vars from the shell.
But if someone has installed Fink/DarwinPorts, but did not setup their shell's PATH, then Gem's configure would not find the things. That's what that chunk does, make sure ./configure will find stuff there.
I think it's pretty safe, it's just adding paths to the PATH variable.
.hc
mfa.sdr IOhannes
------------------------------------------------------------------------ ----
All information should be free. - the hacker ethic