From f2112d0baa379e01d7ce8a961005f5b7c102d9a9 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Fri, 5 Jul 2024 13:52:40 -0400 Subject: Revert "Clarify mutable objects usage" This reverts commit 9f02d0a3e5a5ffc82256391c244b1af38e41ef78. It turns out that this does introduce a behavioral change in existing users of ConfigurationData, which it wasn't supposed to (it was supposed to preserve behavior there, and add a new *warning* for EnvironmentVariables). This breaks projects such as pulseaudio, libvirt, and probably more. Roll back the change and try again after 1.5.0 is released. Fixes: #13372 --- docs/markdown/Configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/markdown/Configuration.md') diff --git a/docs/markdown/Configuration.md b/docs/markdown/Configuration.md index b5875e55e..48f071e6c 100644 --- a/docs/markdown/Configuration.md +++ b/docs/markdown/Configuration.md @@ -39,7 +39,7 @@ use a single `configuration_data` object as many times as you like, but it becomes immutable after being passed to the `configure_file` function. That is, after it has been used once to generate output the `set` function becomes unusable and trying to call it causes an error. -*Since 1.5.0* Copy of immutable `configuration_data` is however mutable. +Copy of immutable `configuration_data` is still immutable. For more complex configuration file generation Meson provides a second form. To use it, put a line like this in your configuration file. -- cgit v1.2.3