Strongswan has an horde of optional plugins, as can bee seen in . Most, if not all, of them are not enabled by default. A possible solution is to add a USE flag for each plugin. An alternative can be to give a USE flag only to main plugins and hide all other behind an "extra" USE flag or something like this.
Steps to Reproduce:
1. Try to use the (ssh-)agent plugin or unity plugin
2. Connection will fail because the plugin is missing
Created attachment 383046 [details, diff]
patch for strongswan-5.2.0-r1.ebuild
How about something like this?
I have added a USE_EXPAND for strongswan_plugins. It works for me but I have not tested unbound (dont use it) nor padlock (I dont have the crypto processor).
Fixed in 5.2.0-r1 , thanks for helping :)
This has been added to the ebuild but the strongswan_plugins has not been added as a USE_EXPAND variable.
it needs to be added to profiles/base/make.defaults.
At the bottom on:
Commit message: Add USE=gmp to control the gmp plugin