Is the mutual exclusion of dco and iproute2 still necessary?
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Description
AFAICS the --enable-iproute2 and --enable-dco configure options were made mutually exclusive, because at the time iproute2 was not able to create ovpn interfaces. This appears to be possible now at least on newer distributions and when the ovpn module is loaded.
Therefore I suggest to remove the code that prevents using these two options together from configure.ac.
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
Start in configure.ac by locating the validation that makes --enable-iproute2 and --enable-dco mutually exclusive. Check the surrounding configuration logic and run the configure step with both options enabled. Done means the combination is accepted without removing unrelated option checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 70/100