Kurt D. Zeilenga writes: > Autoconf already provides a mechanism (config.site) for adjusting > defaults for your site. This mechanism could be used to augment > user specified environmental variables. Only if you document it and document how to translate an option to a config.site setting. -- Hallvard
At 03:35 AM 12/23/98 GMT, h.b.furuseth@usit.uio.no wrote: >Kurt D. Zeilenga writes: > >> Autoconf already provides a mechanism (config.site) for adjusting >> defaults for your site. This mechanism could be used to augment >> user specified environmental variables. > >Only if you document it and document how to translate an option to a >config.site setting. Site defaults should be independent of the package being installed. I do not believe it would be wise for me to document how to translate our package specific options using config.site. However, it might be appropriate to state the our configure script is autoconf generated. See 'Setting Site Defaults' section in the autoconf manual for setting site and machine defaults for autoconf generated configuration scripts. http://www.amath.washington.edu/~lf/tutorials/autoconf/autoconf/autoconf.htm l#SEC79
changed notes changed state Open to Closed
moved from Incoming to Build
changed notes
Discussion related to ITS #3.