Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=863836 --- Comment #17 from Pavel Šimerda <psimerda@xxxxxxxxxx> --- (In reply to comment #16) > The correct way to package NM VPN plugins and their daemons is this: Thanks for adding information that I didn't know. > 1) the VPN package itself; does not depend on NEtworkManager or consume any > NetworkManager libraries like libnm-glib or libnm-util. eg, the "vpnc", > "openconnect", "openvpn", etc packages For example, strongswan's charon-nm depends on NetworkManager-glib but I don't know yet what it is and what's the relation between the part that is in strongswan and the part that is in NetworkManager-strongswan. Do you think that charon-nm binary dependency on NetworkManager-glib is bad enough that I should file a bug report with Strongswan? > 2) the NetworkManager VPN plugin itself: eg, the thing that NM talks to via > dbus to start/stop the VPN connection, and any associated components. But > *not* any GUI components. eg, /usr/libexec/nm-vpnc-service and > /usr/libexec/nm-vpnc-service-vpnc-helper and > /etc/NetworkManager/VPN/nm-vpnc-service.name and any translation files for > the core plugin. > > 3) the GNOME desktop GUI pieces, like the auth dialog and connection editor > pane, and associated translations for the GUI parts. > > I realize the existing plugins are not separated like 2 & 3, but we want to > do that in the future. So new plugins should follow that separation. > > For consistency, #2 should be named "NetworkManager-<vpn service>" (ie, > NetworkManager-strongswan) and #3 should be named "NetworkManager-<vpn > service>-gnome" (ie, NetworkManager-strongswan-gnome). Thank you. We're talking about the following packages then. * strongswan (and optionally strongswan-charon-nm) * NetworkManager-strongswan * NetworkManager-strongswan-gnome -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=5WDLo1tNV6&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review