| 29 Jun 2025 |
 emily | NetworkManager-openconnect is part of the GNOME org on the GitLab, not the NetworkManager one | 15:08:49 |
| emily | I suspect that these plugins should move to the GNOME and Plasma configs in line with upstream recommendations for both | 15:09:04 |
| emily | and not be part of the NM module | 15:09:09 |
| emily | I assume Plasma probably has a list of recommended NM packages | 15:09:16 |
| emily | it also does not seem like other distros ship that OpenConnect plugin by default | 15:09:47 |
| emily | I see no upstream recommendations about plugins | 15:09:59 |
| emily | The default value and the number of available plugins is distro-specific. See the section called “Plugins” below for the available plugins. Note that NetworkManager's native keyfile plugin is always appended to the end of this list (if it doesn't already appear earlier in the list). | 15:10:20 |
| emily | from the NetworkManager.conf official docs | 15:10:30 |
 K900 | https://community.kde.org/Distributions/Packaging_Recommendations does not mention NM whatsoever | 15:10:33 |
| emily | https://www.networkmanager.dev/docs/api/1.40/NetworkManager.conf.html#settings-plugins and the list does not include any of that stuff | 15:10:39 |
| emily | I would maybe keep OpenVPN and just kill the rest | 15:11:41 |
| emily | but it would be good to see what e.g. Ubuntu ship | 15:11:46 |
| emily | oh FFS | 15:12:42 |
| emily | hexa (clat on linux when): NM package has a hard openconnect dependency even though NM itself doesn't | 15:13:05 |
| emily | because
- path = nm_utils_file_search_in_paths("openconnect",
- "/usr/sbin/openconnect",
- DEFAULT_PATHS,
- G_FILE_TEST_IS_EXECUTABLE,
- NULL,
- NULL,
- error);
- if (!path)
- return FALSE;
+ path = "@openconnect@/bin/openconnect";
| 15:13:16 |
 hexa | lovely | 15:13:32 |
| emily | it should just look it up in $PATH | 15:13:40 |
| emily | and we can add things to the service's $PATH | 15:13:44 |
| emily | like normal | 15:13:46 |
| emily | it's possible nm_utils_file_search_in_paths even does hat, I don't know what DEFAULT_PATHS is | 15:13:56 |
| emily | we're definitely sure we want this instead of one option to turn on wired DHCP for networkd right? :P | 15:14:20 |
| hexa | yes, we're sure | 15:15:02 |
| hexa | our networkmanager packaging being bad doesn't change that 😄 | 15:15:09 |
| emily | DEFAULT_PATHS is specific to this file and separate from the global NM_PATHS_DEFAULT | 15:15:17 |
| K900 | In reply to @emilazy:matrix.org
we're definitely sure we want this instead of one option to turn on wired DHCP for networkd right? :P Yeah especially for wireless | 15:15:20 |
| emily | very cool | 15:15:25 |
| emily | and it does not check actual $PATH | 15:15:45 |
| hexa | do we really need modemmanager on the installer iso though? | 15:15:51 |
 @saiko:knifepoint.net | why not just iwd for wireless? | 15:16:01 |
| hexa | to pull multiple gigabytes of outputs from the cache | 15:16:13 |
