strongswan: use --disable-defaults?
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @pprindeville @Thermi
Environment: (put here arch, model, OpenWrt version)
Description:
The errors from https://github.com/openwrt/packages/pull/19128#issuecomment-1207487710 can happen again when strongSwan add new plugins that are enabled by default in a new release. I wonder if it would be a bad idea if we add --disable-defaults to the configure args? This will make strongSwan only use explicitly enabled packages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the strongSwan package configuration and the errors described in openwrt/packages#19128, especially the linked issue comment. Determine whether the configure arguments can disable default plugins while retaining explicitly enabled packages. Done means the package builds with the intended plugin selection and the reported errors are addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100