Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=863836
Dan Williams dcbw@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dcbw@redhat.com
--- Comment #16 from Dan Williams dcbw@redhat.com --- The correct way to package NM VPN plugins and their daemons is this:
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
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).