Enhancement: Extend CI workflow to test library detection with manually compiled dependencies
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- cpp, github-actions, linux
- 领域
- build-system, ci-cd, devops
调研方向
首先检查当前的 GitHub Actions 工作流和 configure 脚本，然后使用 issue #3404 和 #3318 了解库检测情况。添加涵盖在所列发行版和安装路径中手动编译的 YAJL、LMDB 和 PCRE2 的作业；完成的标准是 configure 脚本能够在这些场景中成功检测到每个依赖项。
由索引模型根据 Issue 内容生成。
描述
Background
This issue is a follow-up to #3404, where we identified that the ModSecurity configure script fails to detect YAJL, LMDB, and PCRE2 libraries when they are installed in lib64 directories or other non-standard paths.
While the library detection fix has been submitted via PR, @airween suggested an important enhancement to extend the CI workflow to better test these scenarios.
Current CI Limitations
The current CI workflow primarily tests library detection using OS package managers, which typically install libraries in standard system paths. However, many users compile libraries manually and install them in custom locations, particularly:
/usr/local/[library]/lib64/directories- Custom prefix paths
- Container environments with non-standard library layouts
Proposed Enhancement
Add new CI jobs that test the configure script's library detection capabilities with manually compiled dependencies, specifically:
1. Manual Library Compilation Testing
- Compile YAJL, LMDB, and PCRE2 from source
- Install them in various custom paths (lib64, custom prefixes)
- Verify configure script correctly detects these libraries
2. Multi-Distribution Testing
Test across various Linux distributions that commonly use lib64:
- Alma Linux 9, 10
- CentOS Stream 9, 10
- Oracle Linux 9, 10
- Rocky Linux 9, 10
- Ubuntu 22.04, 24.04
- Debian 12, 13
- OpenSUSE
- Fedora
3. Container Environment Testing
- Test in containerized environments where libraries are often manually compiled
- Verify compatibility with different base images
Benefits
- Improved Reliability: Catch library detection issues before they reach users
- Better Coverage: Test real-world scenarios where users compile dependencies manually
- Cross-Platform Validation: Ensure compatibility across diverse Linux distributions
- Regression Prevention: Prevent future breakage of library detection logic
Implementation Approach
- Create new GitHub Actions workflow jobs
- Add matrix builds for different distributions and library installation methods
- Implement automated testing scripts for manual library compilation
- Add validation steps to ensure configure script works correctly
Related Issues
- #3404 - Original lib64 detection issue
- #3318 - Similar PCRE2 detection problems
Note: This enhancement would significantly improve the project's build system reliability and help prevent similar issues in the future. I'm ready to contribute to implementing these CI improvements.
- 主要语言
- C++
- 星标
- 9.8k
- 派生
- 1.8k
- 平均合并
- 2 小时 46 分钟
- 30 天内合并 PR
- 1
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
owasp-modsecurity/ModSecurity 的其他 Issue
-
2.x Platform - IIS
难度 1/5 1 小时以内 新手友好度 90/100
owasp-modsecurity/ModSecurity#3623 · 1 条评论 ·
维护者通常 1 天内回复
-
2.x Platform - IIS
难度 2/5 1-3 小时 新手友好度 82/100
owasp-modsecurity/ModSecurity#3621 · 1 条评论 ·
维护者通常 1 天内回复
-
2.x Platform - IIS
难度 2/5 1-3 小时 新手友好度 84/100
owasp-modsecurity/ModSecurity#3619 · 1 条评论 ·
维护者通常 1 天内回复
-
2.x Platform - IIS
难度 2/5 1-3 小时 新手友好度 76/100
owasp-modsecurity/ModSecurity#3612 · 1 条评论 ·
维护者通常 1 天内回复
-
3.x
难度 2/5 1-3 小时 新手友好度 70/100
owasp-modsecurity/ModSecurity#3580 · 1 条评论 ·
维护者通常 1 天内回复
查看 owasp-modsecurity/ModSecurity 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 92/100
espressif/esp-matter#1867 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
isce-framework/isce3#387 ·
-
upstream update
难度 2/5 1-3 小时 新手友好度 68/100
conan-io/conan-center-index#31055 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复