diff options
| author | Mats Wichmann <mats@linux.com> | 2024-03-17 12:25:49 (GMT) |
|---|---|---|
| committer | Mats Wichmann <mats@linux.com> | 2024-09-04 22:01:28 (GMT) |
| commit | 706f0aff7972d4c055eaabcf2e084c7036a70d5d (patch) | |
| tree | 3500bb9d7733fce5b4aae6eac939a199e141814f /RELEASE.txt | |
| parent | b2a103bff8787f9de51af975eae5e57347cdac80 (diff) | |
| download | SCons-706f0aff7972d4c055eaabcf2e084c7036a70d5d.zip SCons-706f0aff7972d4c055eaabcf2e084c7036a70d5d.tar.gz SCons-706f0aff7972d4c055eaabcf2e084c7036a70d5d.tar.bz2 | |
Don't let deletions leak from OverrideEnvironment
Previously, deleting from an OverrideEnvironment removed not just the
override item but also the same item in the subject (base) environment.
This prevents supplying the value from the subject, as that would be
contrary to the expectation after "I deleted this variable". However,
this lets the override modify its subject, a form of leakage we don't
want. Now a deleted item has its key recorded to prevent refilling
later. Direct assignment will still set the item back in the override.
rpm packaging tool: call Override factory method rather than directly
instantiating OverrideEnvironment ("best practices")
Signed-off-by: Mats Wichmann <mats@linux.com>
Diffstat (limited to 'RELEASE.txt')
| -rw-r--r-- | RELEASE.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASE.txt b/RELEASE.txt index 439c863..ce51f3a 100644 --- a/RELEASE.txt +++ b/RELEASE.txt @@ -29,6 +29,11 @@ CHANGED/ENHANCED EXISTING FUNCTIONALITY - List modifications to existing features, where the previous behavior wouldn't actually be considered a bug +- Override envirionments, created when giving construction environment + keyword arguments to Builder calls (or manually, through the + undocumented Override method), were modified not to "leak" on item deletion. + The item will now not be deleted from the base environment. + FIXES ----- |