From 34e883d6da1c6819a17fc11b8e3ab9f8e3ae4e46 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Wed, 18 Dec 2024 14:03:10 +0000 Subject: [PATCH] NEWS: Add notes about Meson behaviour not being identical to Autotools See dbus/dbus#542 for an example of one particularly significant behaviour change. Signed-off-by: Simon McVittie (cherry picked from commit 8ca823d38f4d028b7844f204b1787bbc03b3a0f4) --- NEWS | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/NEWS b/NEWS index fb3d66f8..e49a9b90 100644 --- a/NEWS +++ b/NEWS @@ -32,6 +32,21 @@ Build system and dependencies: Behaviour changes: +• As a result of the move from Autotools to Meson as the recommended + build system on Unix, the names of all build-time options have changed. + Not all Meson options are a 1:1 replacement for their closest equivalent + in Autotools, so the options used for a dbus build should be reviewed. + +• If `meson install` is run as root, and traditional (non-systemd) + activation is enabled, the ownership and setuid permission of + dbus-daemon-launch-helper are not set automatically. + This is not the same as the historical behaviour of the Autotools build + system, which would set the ownership and permissions automatically if + run as uid 0. + The ownership and permissions must now be set by OS distribution packaging, + or as a manual post-installation step if dbus is installed directly + without going via a packaging system (which is not recommended). + • On Unix, the well-known system bus socket is in the runtime state directory by default (normally /run) (see 1.15.4 for more details)