[MacPorts] #35867: libarchive: update to 3.0.4
#35867: libarchive: update to 3.0.4 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libarchive -------------------------------------+-------------------------------------- {{{ $ port livecheck libarchive libarchive seems to have been updated (port version: 2.8.5, new version: 3.0.4) }}} -- Ticket URL: <https://trac.macports.org/ticket/35867> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Changes (by toby@…): * status: new => assigned Comment: Latest version is 3.1.2. Problem is that libarchive 3.x isn't binary compatible with 2.x, so we'll need to chase dependencies. -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Comment (by mfeiri@…): When talking about binary compatibility you are thinking of something like rev bumping all dependents, e.g. as in http://trac.macports.org/changeset/69520 for openssl 0.9.8->1.0.0, right? AFAIK the new 'rev-upgrade' action in MacPorts 2.1 should handle this automatically. It "... checks for and rebuilds ports that may have become incorrectly linked when a dependency was upgraded to a new, binary- incompatible version. This runs automatically after upgrades and installs ...", see http://trac.macports.org/browser/trunk/base/NEWS and https://trac.macports.org/wiki/SummerOfCode2011#rev-upgrade There is a small chance that some ports are not API compatible with version 3 of libarchive. A quick grep through the dports hierarchy reveals just 5 ports (hydrogen, elftoolchain, gvfs, epic5, ark) that actually depend on libarchive. Verifying that these 5 ports still build/work properly after the patch in #38164 is applied should be all we need. -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Comment (by toby@…): Yes, I believe it's just ABI compatibility, the API is (mostly) unchanged. -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Comment (by ryandesign@…): rev-upgrade is only there to help users when maintainers forget to increase revisions to make ports rebuild. Increasing revisions when library versions change is still the correct solution. Just think what would happen if we didn't: users might get a binary from our packages server which rev-upgrade would immediately declare broken and have to rebuild. -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Comment (by mfeiri@…): Thanks ryandesign, I didn't consider the pre-built binaries. I've tried the patch from #38164 and it worked perfectly fine for me with elftoolchain, gvfs, and ark. It turned out that hydrogen doesn't actually use libarchive and epic5 is broken for other reasons. AFAICT the upgrade to libarchive 3 should be okay. -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#35867: libarchive: update to 3.x ---------------------------+---------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: libarchive | ---------------------------+---------------------- Comment (by egall@…): Another option could be making a separate port for libarchive3... -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#35867: libarchive: update to 3.x ---------------------------+-------------------- Reporter: ryandesign@… | Owner: toby@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: libarchive | ---------------------------+-------------------- Changes (by mfeiri@…): * status: assigned => closed * resolution: => fixed Comment: Updated in r107252 (maintainer timeout) -- Ticket URL: <https://trac.macports.org/ticket/35867#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts