Mats Wichmann

@bdbaddog what do you think? My reaction is to say "that's not the SCons way, if you want something from `os.environ` be explicit about it", but it seemed like there...

Implementing is easy, but... paraphrasing the above, we have two ways: ```bash $ BUILDTYPE=DEBUG scons $ scons BUILDTYPE=DEBUG ``` I'm not feeling massive motivation to need the first type when...

It's an entirely different topic, but we maybe ought to find a more clever way to update individual fields of `ENV`. Other construction vars are mostly okay to do things...

I changed the summary slightly. This is proposing a moderately serious bit of rework - swap how the dual gobal/environment methods are defined/attached - which seems to have little real...

Okay, this says: undocumented `File().exists()` method and undocumented `env.Detect()` method - do those need to be added to the docs?

Right, that's what the issue is; it's the commentary that suggests workarounds - two of which it notes are undocumented.

Where would one document this? Is there a document targeted at tool writers? Certainly doesn't seem like a manpage candidate.

Maybe Tools chapter in userguide, to follow the Builder section? Not sure I could volunteer to write that though. So the wiki page I guess is the best first step.

Hmmm, this claims the doc section was removed, but it still has this wording: > The value may also be set, using `SetOption` or `env.SetOption()`, if conditions in a `SConscript`...

No, I don't think so. The text pasted above still suggests an AddOption'd option might be able to be the subject of SetOption, but this is not true, it only...