strongswan: Add dependency to virtual package strongswan-mod-socket

[Thermi]

Required to model the dependency of the charon daemon onto one of the two socket abstractions Otherwise none will be installed and the daemon is not usable

Closes #16261

Signed-off-by: Noel Kuntze [email protected]

Maintainer: me / @pprindeville Compile tested: x86_64, trunk Run tested: Not yet

Description:

[neheb]

Needs a rebase.

[Thermi]

Builds for me.

[pprindeville]

Needs a rebase.

[Thermi]

Builds and constructs the right dependencies here. strongswan-full and -minimal (metapackages) depend on socket-default, but strongswan-charon depends on strongswan-mod-socket, which is a virtual package provided by -socket-default and -socket-dynamic. So if somebody wants to uninstall -socket-default but has socket-default and -socket-dynamic, dependencies of strongswan-full and -minimal will not be satisfied anymore. If the user uninstalls them then the only dependencies on strongswan packges that are from an explicitly installed packages are from -mod-socket-dynamic which requires strongswan and libc. strongswan only packages libstrongswan. So in total if somebody switches to -socket-dynamic, removes -socket-default, and removes all unrequired packages, they will have an incomplete and unusable installation of strongwan. We could fix that by making -full and -minimal depend on -mod-socket. So it's a dependency on the virtual package.

@pprindeville thoughts?

[Thermi]

All the other expressions in the file have exactly one plus. Do you know better in that regard? It still throws syntax errors when building.

[pprindeville]

Is this still open?