With bind mounts, the directories we bind mount to get recorded as the meson source and build directories. This means meson will complain if we later try to run meson install -C /work/build in the virtual machine or container. If we use symlinks, the directories we symlink to will be recorded as the meson source and build directories, which means meson install -C /work/build will work when executed after booting the VM or container. I tried to do the same for debian as well but the debian package tooling changes directory into the build directory and then does meson setup .. which is completely broken when switching to a symlink.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack