Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Emmanuele Bassi <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

The "emit a critical warning if your object notifies a property during
finalization" entry should have been added in 2.75.1, but better late
than never.

Signed-off-by: Philip Withnall <[email protected]>

Natanael Copa authored Oct 05, 2022 and Philip Withnall committed Jan 25, 2023

Keep the API for ABI compatibility.

See
!2935 (comment 1650099)
for a summary of the reasoning for this change:
 - The performance of system-provided allocators has improved since
   GSlice was written, and they are now similarly as performant, or more
   performant, than GSlice.
 - The code is unmaintained and nobody understands it.
 - It doesn’t integrate with tooling and system security features which
   have been written for the system `malloc()` implementation (such as
   sanitisers, valgrind, etc.).
 - It’s confusing for developers: should they use `g_slice_new()` or
   `g_new()`?
 - GSlice is faster than the libc allocator for allocating and
   (particularly) freeing linked lists, but since these are a rubbish
   data structure, that’s not a great thing to optimise for.

For the cases where application performance is negatively impacted by
the implementation of GSlice being dropped (and we don’t think there’ll
be many), applications can use a drop-in `malloc()` replacement which is
more suited to their particular workload. Choosing an allocator in GLib
to suit all application workloads is not possible.

Including documentation updates and cleanups by Philip Withnall.

Fixes: #1079

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

This reworks commit 20e1508e, for two
reasons:
 - Upstream dbus.git now does the same (although this isn’t yet reflected
   in the online version of the D-Bus Specification); see
   https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/209.
 - It allows local-prefix (e.g. jhbuild) builds of GLib to build in a
   custom prefix while still interacting with system services using the
   system-wide `/run` directory. To do so, pass `-Druntime_dir=/run` to
   meson configure.

As documented in the `NEWS` file in
https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/209, it’s only
valid to use `/run` – rather than `/var/run` – for D-Bus if the two
paths are interoperable. i.e. `/var/run` should be a symlink to `/run`,
and the D-Bus daemon should be configured to put its socket there.

This commit deliberately doesn’t introduce a special `system_socket`
configure option for specifying where the D-Bus system socket lives, as
that would only be useful for a distribution which sets `runstatedir` to
something other than `/var/run` or `/run`, which seems unlikely. We
could add such an option in future, though, if a distribution comes
forward with such a requirement.

See discussion on
!3095 (comment 1605502)

.

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

ISO 8601, please.

Signed-off-by: Philip Withnall <[email protected]>

Signed-off-by: Marco Trevisan (Treviño) <[email protected]>

Co-authored-by: Matthias Clasen <[email protected]>
Signed-off-by: Marco Trevisan (Treviño) <[email protected]>

Co-authored-by: Matthias Clasen <[email protected]>
Signed-off-by: Marco Trevisan (Treviño) <[email protected]>

Signed-off-by: Philip Withnall <[email protected]>

As per review comment, this is miscellaneous enough that it could be
forgotten about at release time, but should still be mentioned.
Guarantee it by starting work on that now.

Signed-off-by: Philip Withnall <[email protected]>

Not clear why they were separate files. This is a bit tidier.

Signed-off-by: Philip Withnall <[email protected]>