Opened 10 years ago
Closed 10 years ago
#44482 closed update (fixed)
Yaz updated from 4.2.63 to 5.4.0
| Reported by: | coateconnection (David Coate) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch, maintainer | Cc: | |
| Port: | yaz |
Description
Yaz 5 is not api compatible with Yaz 4
Attachments (2)
Change History (7)
Changed 10 years ago by coateconnection (David Coate)
| Attachment: | yaz-Portfile.diff added |
|---|
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
David sent the following reply by email:
Yaz 5 has incompatible ABI from Yaz 4, and per developer - "The API has also been changed in a few places.. Most software using YAZ will need no or little modification. In particular the ZOOM API is unchanged since YAZ 4” . All the Index Data programs are Yaz 5 so the only port left is p5-net-z3950-zoom. It has no-maintainer but I suspect based on the above it will work as well. I think we should move the yaz port to version 5 and if the need exist, make a Yaz4 port for p5-net-z3950-zoom.
comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Status: | new → assigned |
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
5.4.0 is available. Should we go straight to that? It builds for me, and the ports that depend on yaz still do too.
Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Attachment: | yaz-5.4.0.diff added |
|---|
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
| Summary: | Yaz updated from 4.2.63 to 5.3.0 → Yaz updated from 4.2.63 to 5.4.0 |
Note: See
TracTickets for help on using
tickets.
Did you mean not ABI compatible or not API compatible? If not ABI compatible, then all ports that link with yaz need to have their revisions increased so that they'll be rebuilt. If not API compatible, then we should keep the yaz port at version 4 and add a new yaz5 port for yaz version 5, unless all ports that link with yaz already detect and use the new yaz 5 API.