Doug Barton wrote: > Traditionally the precedence has been: > > make.conf < OPTIONS < command line
Are you sure? But how did the old framework find out if a WITH_* / WITHOUT_* variable came from make.conf or from the command line? For example, say the make environment contains WITH_FOO=YES, but the OPTIONS file contains WITHOUT_FOO=YES. If the above precedence is to be followed, then the framework needed to find out whether the WITH_FOO setting came from make.conf or from the command line. I don't think there's an easy way to do that. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python tricks" is a tough one, cuz the language is so clean. E.g., C makes an art of confusing pointers with arrays and strings, which leads to lotsa neat pointer tricks; APL mistakes everything for an array, leading to neat one-liners; and Perl confuses everything period, making each line a joyous adventure <wink>. -- Tim Peters _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[email protected]"
