Hi Yves-Alexis, > Sorry for breaking your use case, I didn't really check the reverse > dependencies of the strongswan metapackage (to be honest that > metapackage was mostly intended for end-users, not packagers).
No worries. Currently network-manager-l2tp package has the following dependency: strongswan | libreswan So that metapackage came in handy as it isn't possible to have dependencies like: (strongswan-starter & strongswan-charon) | libreswan > I think the longterm road is indeed for nm-l2tp to migrate to > either using the VICI interface (to control the charon-systemd > daemon like swanctl(8) does) or maybe to coordinate with > network-manager-strongswan and talk to the charon-nm daemon > (in the strongswan-nm package) over D-Bus. If I go for VICI, sounds like it might be a build time decision to go for either strongswan or libreswan. Or drop libreswan... With D-Bus I guess it could be a runtime decision depending on what is installed, like it is now. > Short term, nm-l2tp needs to depends on the packages it actually > uses. The charon daemon itself is in the strongswan-charon package, > while the strongswan-starter package provides the ipsec(8) command > reading the ipsec.conf to control the daemon through the stroke > plugin. If you need both, then depends on both. As d/control now has strongswan-charon having a dependency on strongswan-starter, I might wait for the next strongswan-charon revision which has that dependency so I could then use something like the following dependency in network-manager-l2tp: strongswan-charon (>= 6.0.0-3) | libreswan Cheers, Doug
