shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-23 21:35:11 +03:00
Code
740cd1e0f2
systemd/network/meson.build

49 lines
1.6 KiB
Meson
Raw Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 07:23:58 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add license headers and SPDX identifiers to meson.build files So far I avoided adding license headers to meson files, but they are pretty big and important and should carry license headers like everything else. I added my own copyright, even though other people modified those files too. But this is mostly symbolic, so I hope that's OK.
2017-11-18 20:32:01 +03:00
build-sys: use #if Y instead of #ifdef Y everywhere The advantage is that is the name is mispellt, cpp will warn us. $ git grep -Ee "conf.set\('(HAVE|ENABLE)_" -l|xargs sed -r -i "s/conf.set\('(HAVE|ENABLE)_/conf.set10('\1_/" $ git grep -Ee '#ifn?def (HAVE|ENABLE)' -l|xargs sed -r -i 's/#ifdef (HAVE|ENABLE)/#if \1/; s/#ifndef (HAVE|ENABLE)/#if ! \1/;' $ git grep -Ee 'if.*defined\(HAVE' -l|xargs sed -i -r 's/defined\((HAVE_[A-Z0-9_]*)\)/\1/g' $ git grep -Ee 'if.*defined\(ENABLE' -l|xargs sed -i -r 's/defined\((ENABLE_[A-Z0-9_]*)\)/\1/g' + manual changes to meson.build squash! build-sys: use #if Y instead of #ifdef Y everywhere v2: - fix incorrect setting of HAVE_LIBIDN2
2017-10-03 11:41:51 +03:00
if conf.get('ENABLE_NETWORKD') == 1
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
install_data(
'80-6rd-tunnel.network',
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
'80-6rd-tunnel.link',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-container-host0.network',
network: configure a tun host0 interface in a container While containers often have their host0 network provided by veth when the container runtime is privileged, unprivileged containers tend to have their network provided via slirp4netns or pasta. These tools use a tun interface rather than a veth interface and systemd should still set configure such networks. We should have different .network files for the veth and tun use cases as there may arise a need to configure them differently. We should not rename 80-container-host0.network as that would cause existing drop-ins to no longer apply. Closes: #32095 Fixes: f139393dd20a ("network: use Kind= instead of Driver=") Signed-off-by: Helmut Grohne <helmut@subdivi.de>
2024-05-15 08:21:53 +03:00
'80-container-host0-tun.network',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-container-vb.network',
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
'80-container-vb.link',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-container-ve.network',
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
'80-container-ve.link',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-container-vz.network',
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
'80-container-vz.link',
nsresourced: add new daemon for granting clients user namespaces and assigning resources to them This adds a small, socket-activated Varlink daemon that can delegate UID ranges for user namespaces to clients asking for it. The primary call is AllocateUserRange() where the user passes in an uninitialized userns fd, which is then set up. There are other calls that allow assigning a mount fd to a userns allocated that way, to set up permissions for a cgroup subtree, and to allocate a veth for such a user namespace. Since the UID assignments are supposed to be transitive, i.e. not permanent, care is taken to ensure that users cannot create inodes owned by these UIDs, so that persistancy cannot be acquired. This is implemented via a BPF-LSM module that ensures that any member of a userns allocated that way cannot create files unless the mount it operates on is owned by the userns itself, or is explicitly allowelisted. BPF LSM program with contributions from Alexei Starovoitov.
2023-04-20 20:07:33 +03:00
'80-namespace-ns.network',
network: add .link file to match 80-namespace.network This file makes clear the interface shall be owned by networkd. This does what 658169e6d307b5b1aea0d82b4a6430fa9d529c68 did for nspawn's regular devices for the devices defined through 8aee931e7ae1adb01eeac0e1e4c0aef6ed3969ec too.
2024-04-22 18:30:58 +03:00
'80-namespace-ns.link',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-vm-vt.network',
network: take explicit ownership of our own interfaces This is a follow-up for #30786 and uses it to assign ID_NET_MANAGED_BY=io.systemd.Network to all all network interfaces that we consider ours to manage. This should hopefully have the effect that other well-behaving managers won't fight for these devices. This doesn't bother with network interfaces we match inside containers, since udev is not available there anyway.
2024-01-10 18:18:41 +03:00
'80-vm-vt.link',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-wifi-adhoc.network',
network: add meson option to rename .example files on install Also this renames 80-ethernet.network.example -> 89-ethernet.network.example, to make it have lower precedence over other default .network files for Ethernet interfaces. Closes #29765.
2023-11-02 08:12:42 +03:00
install_dir : networkdir)
example_network_files = files(
'80-auto-link-local.network.example',
'89-ethernet.network.example',
meson: install newly added example .network file Follow-up for e6ba085398866ab05511fe748b8e9f7cbe85148e.
2023-11-02 07:18:45 +03:00
'80-wifi-ap.network.example',
'80-wifi-station.network.example',
network: add meson option to rename .example files on install Also this renames 80-ethernet.network.example -> 89-ethernet.network.example, to make it have lower precedence over other default .network files for Ethernet interfaces. Closes #29765.
2023-11-02 08:12:42 +03:00
)
meson: always install network example files I started working on integrating this in the Fedora package and realized that the example files should be installed regardless of the renamed files when default-network=true is used. This is because the renamed files become part of a different package, and we want to have the other files which are used as documentation in the main package anyway.
2023-11-23 02:06:29 +03:00
install_data(
example_network_files,
install_dir : networkdir)
network: add meson option to rename .example files on install Also this renames 80-ethernet.network.example -> 89-ethernet.network.example, to make it have lower precedence over other default .network files for Ethernet interfaces. Closes #29765.
2023-11-02 08:12:42 +03:00
if get_option('default-network')
foreach f : example_network_files
install_data(
f,
meson: fix install path of example .network files It seems that when 'rename' field is set, the path (instead of the filename) is appended to the 'install_dir'. Follow-up for 9b7a624267fddc5c20bd15480e7a393d7a3b270e. Fixes #29925.
2023-11-08 15:52:38 +03:00
rename : fs.replace_suffix(fs.name(f), ''),
network: add meson option to rename .example files on install Also this renames 80-ethernet.network.example -> 89-ethernet.network.example, to make it have lower precedence over other default .network files for Ethernet interfaces. Closes #29765.
2023-11-02 08:12:42 +03:00
install_dir : networkdir)
endforeach
endif
meson: build systemd using meson It's crucial that we can build systemd using VS2010! ... er, wait, no, that's not the official reason. We need to shed old systems by requring python 3! Oh, no, it's something else. Maybe we need to throw out 345 years of knowlege accumulated in autotools? Whatever, this new thing is cool and shiny, let's use it. This is not complete, I'm throwing it out here for your amusement and critique. - rules for sd-boot are missing. Those might be quite complicated. - rules for tests are missing too. Those are probably quite simple and repetitive, but there's lots of them. - it's likely that I didn't get all the conditions right, I only tested "full" compilation where most deps are provided and nothing is disabled. - busname.target and all .busname units are skipped on purpose. Otherwise, installation into $DESTDIR has the same list of files and the autoconf install, except for .la files. It'd be great if people had a careful look at all the library linking options. I added stuff until things compiled, and in the end there's much less linking then in the old system. But it seems that there's still a lot of unnecessary deps. meson has a `shared_module` statement, which sounds like something appropriate for our nss and pam modules. Unfortunately, I couldn't get it to work. For the nss modules, we need an .so version of '2', but `shared_module` disallows the version argument. For the pam module, it also didn't work, I forgot the reason. The handling of .m4 and .in and .m4.in files is rather awkward. It's likely that this could be simplified. If make support is ever dropped, I think it'd make sense to switch to a different templating system so that two different languages and not required, which would make everything simpler yet. v2: - use get_pkgconfig_variable - use sh not bash - use add_project_arguments v3: - drop required:true and fix progs/prog typo v4: - use find_library('bz2') - add TTY_GID definition - define __SANE_USERSPACE_TYPES__ - use join_paths(prefix, ...) is used on all paths to make them all absolute v5: - replace all declare_dependency's with [] - add more conf.get guards around optional components v6: - drop -pipe, -Wall which are the default in meson - use compiler.has_function() and compiler.has_header_symbol instead of the hand-rolled checks. - fix duplication in 'liblibsystemd' library name - use the right .sym file for pam_systemd - rename 'compiler' to 'cc': shorter, and more idiomatic. v7: - use ENABLE_ENVIRONMENT_D not HAVE_ENVIRONMENT_D - rename prefix to prefixdir, rootprefix to rootprefixdir ("prefix" is too common of a name and too easy to overwrite by mistake) - wrap more stuff with conf.get('ENABLE...') == 1 - use rootprefix=='/' and rootbindir as install_dir, to fix paths under split-usr==true. v8: - use .split() also for src/coredump. Now everything is consistent ;) - add rootlibdir option and use it on the libraries that require it v9: - indentation v10: - fix check for qrencode and libaudit v11: - unify handling of executable paths, provide options for all progs This makes the meson build behave slightly differently than the autoconf-based one, because we always first try to find the executable in the filesystem, and fall back to the default. I think different handling of loadkeys, setfont, and telinit was just a historical accident. In addition to checking in $PATH, also check /usr/sbin/, /sbin for programs. In Fedora $PATH includes /usr/sbin, (and /sbin is is a symlink to /usr/sbin), but in Debian, those directories are not included in the path. C.f. https://github.com/mesonbuild/meson/issues/1576. - call all the options 'xxx-path' for clarity. - sort man/rules/meson.build properly so it's stable
2017-04-05 06:03:47 +03:00
endif
meson: fix condition for installation of .in units, 99-default.link The condition to install in_units was calculated, but not used. 99-default.link should be installed uncoditionally.
2017-04-14 03:17:04 +03:00
install_data('99-default.link',
install_dir : networkdir)
meson: /etc/systemd/network is also used by udevd
2023-11-02 08:20:11 +03:00
if install_sysconfdir
install_emptydir(sysconfdir / 'systemd/network')
endif
Copy Permalink