[MacPorts] #43174: perl5.14: upgrade to 5.14.4
#43174: perl5.14: upgrade to 5.14.4 ---------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: perl5.14 ---------------------+-------------------------------- I'm attaching a patch for upgrading Perl 5.14 to 5.14.4. The only problem that I don't understand is the following. Currently more or less all packages depending on Perl5.14 store files under {{{ /opt/local/lib/perl5/vendor_perl/5.14.2/ }}} while after the update they would store the files under {{{ /opt/local/lib/perl5/vendor_perl/5.14.4/ }}} This means than all(?) Perl ports would need a revbump to put the files to proper location, but browsing through the history of version upgrades of Perl ports I don't see such revbumps. I also have all of the following (non-empty) folders under `/opt/local/lib/perl5/vendor_perl`: * 5.16.0/ * 5.16.1/ * 5.18.1/ * 5.18.2/ which seems a bit weird. -- Ticket URL: <https://trac.macports.org/ticket/43174> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: perl5.14 | -----------------------+-------------------------------- Comment (by jmr@…): Finding modules installed by older versions is what inc_version_list is for, so you need to add the previous version to it every time you update. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Changes (by ryandesign@…): * keywords: => haspatch -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by mojca@…): @jmr: thanks, I uploaded a new patch taking this into account. I also added a patch to upgrade 5.16.1 to 5.16.3 to #43150 (along with another patch). Version 5.12.4 needs an upgrade to 5.12.5 too. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by mojca@…): OK, so the only remaining question is: should I bother about #43157 or should I commit this (and do a revbump later in case it turns out necessary to fix something in core perl)? -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by macsforever2000@…): I don't know enough about perl to comment about #43157, but applying the version update makes sense in any event. Go for it. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by mojca@…): I committed the update in r119338 (and sadly forgot to reference the ticket). However I believe that a number of ports might need a revbump. I have absolutely no clue which ones. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by mojca@…): Now that I updated 5.14, I also took the chance to update 5.12 in r119339. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by jmr@…): Replying to [comment:7 mojca@…]:
However I believe that a number of ports might need a revbump. Why?
-- Ticket URL: <https://trac.macports.org/ticket/43174#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Comment (by mojca@…): One of the reasons is that {{{ ${prefix}/lib/perl5/5.12.4/darwin-thread-multi-2level/CORE/libperl.dylib }}} gets moved to {{{ ${prefix}/lib/perl5/5.12.5/darwin-thread-multi-2level/CORE/libperl.dylib }}} for example and all binaries or libraries linking against `libperl.dylib` become broken. (I had two broken libraries here for example.) From what I understand the dylibs are ABI-compatible within minor version updates, but the change of location isn't really helping us here. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#43174: perl5.14: upgrade to 5.14.4 -----------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: perl5.14 | -----------------------+-------------------------------- Changes (by mojca@…): * status: new => closed * resolution: => fixed Comment: I'm closing this ticket. I updated Perl 5.12 and 5.14 (5.16 was also updated recently). I opened a new ticket addressing incompatibilities between updates (#43480). The need for revbumping ports is still there, but I don't know which ones need a revbump. Let's open new tickets or just commit those changes when the need arises / when you figure out that ports were broken. -- Ticket URL: <https://trac.macports.org/ticket/43174#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts