mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2025-12-28 21:30:10 +01:00
It is not clear whether we can actually respect this value. For example, we should not restore the kernel's default value on deactivation or device's state change, but it is unclear if we can ensure that we'll still have the connection's configuration in all possible changes of state. Also, it is unclear if it's a desirable value that we want to support. At this point it is mostly clear that trying to configure NM managed devices externally always ends being dissapointing, no matter how hard we try. Remove this value for now, while we discuss whether it makes sense or not, so it doesn't become stable in the new 1.54 release. |
||
|---|---|---|
| .. | ||
| tests | ||
| meson.build | ||
| nm-meta-setting-access.c | ||
| nm-meta-setting-access.h | ||
| nm-meta-setting-base-impl.c | ||
| nm-meta-setting-base-impl.h | ||
| nm-meta-setting-base.h | ||
| nm-meta-setting-desc.c | ||
| nm-meta-setting-desc.h | ||
| README.md | ||
| settings-docs.h.in | ||
libnmc-setting
A client library on top of libnm (and libnm-base). Like libnmc-base, this is a helper library that a libnm client could use.
But its purpose is more specific. It's mainly about providing a generic API for handling connection properties. As such, it's only used by nmcli and in practice also specific to nmcli.
Theoretically, the API is supposed to be generic, so we could imagine another client that uses this beside nmcli.
Like libnm-base, this has a similar purpose and application as ../libnm-client-aux-extern/, the difference is that it's even more specific.