AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO
[minizip] Is it really mandatory the use of minizip-ng compared to minizip provided by zlib?
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 503
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
[Talking with my Debian Developer hat on]
I'm trying to package OCIO v2.3.2 in Debian and it seems like I'm forced to package minizip-ng tool as well because the building process won't pass the initial checks without that build dependency.
As far as I understand it, minizip-ng is just a simpler version of the minizip tool (now merged in zlib, already in Debian archives) so I'm wondering if it's not possible to use the "normal" minizip library as an alternative to the -ng version, maybe allowing the [Findminizip-ng](https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/main/share/cmake/modules/Findminizip-ng.cmake) module to search for both, prioring the -ng version. That would allow me to upgrade the package in Debian quicker.
Thanks.
Contributor guide
Research direction
Start with share/cmake/modules/Findminizip-ng.cmake and the initial build checks that require the dependency. Compare how the module searches for minizip-ng and the zlib-provided minizip, then determine whether both can be supported with minizip-ng preferred. Done means the Debian packaging build passes without requiring minizip-ng when the compatible alternative is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100