Bug 1218713
| Summary: | There have been new releases of Zipios++ | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Russel Winder <russel> |
| Component: | zipios++ | Assignee: | Richard Shaw <hobbes1069> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | hobbes1069, john |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-25 21:14:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Russel Winder
2015-05-05 16:15:57 UTC
I looked at updating it a few weeks ago but there have been MAJOR changes to the API and FreeCAD will not work with the 2.0.2 release. One one hand, I'm glad someone has revived the project, but the changes should have been more incremental. One of the major purposes of the work was to update the code to C++11 (I wanted C++14, but Alexis convinced to me to go only to C++11). This is a revolutionary change of C++, it was therefore entirely right to review the API in the light of C++11, removing the Java-isms and bringing in C++-isms. So yes this is a major revision of the API and clearly there are breaking changes. Incremental changes were not really appropriate for this work, hence the major version being incremented to 2. My assumption had been that with both Debian and Fedora, Zipios++ 0.1.5.9 would be retained and that Zipios++ 2.0.2 would be added so that both libraries were present, allowing using projects to upgrade in their own time. Works for me, but it does mean that it will have to go through a Review Request. The package name should probably be zipios (minus the ++). Typically we would append the major soversion but what happens when you bump it to 3? The other option would be to do a new review request for the current version and name it zipios++0 which is ok because it would never increment and then update the current package to 2.0.X. Review request has been submitted... |