openresty / openresty/openresty-packaging
add --with-compat by default
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 187
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
without this flag, building dynamic modules, targeting a specific openresty package release is a pain. One has to use -V option to figure out the build arguments used when building the official release and jsut a copy/pasted does not work since paths are not the same
Is this flag missing on purpose?
with this flag one basically needs just ./configure --with-compat --add-dynamic-module=..
Contributor guide
No contributing guide indexed for this repository
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 at the packaging entry point that invokes ./configure and compare its arguments with the official release details shown by -V. Check how adding --with-compat affects --add-dynamic-module=.. builds, and consider the work done when dynamic modules can target a package release without copying release-specific paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100