Opened 10 years ago

Closed 10 years ago

#43174 closed update (fixed)

perl5.14: upgrade to 5.14.4

Reported by: mojca (Mojca Miklavec) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: markemer (Mark Anderson), jmroot (Joshua Root), mf2k (Frank Schima), mf2k (Frank Schima), cooljeanius (Eric Gallager)
Port: perl5.14

Description

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.

Attachments (2)

perl5.14.4.diff (3.0 KB) - added by mojca (Mojca Miklavec) 10 years ago.
perl5.14.4.2.diff (3.5 KB) - added by mojca (Mojca Miklavec) 10 years ago.

Download all attachments as: .zip

Change History (14)

Changed 10 years ago by mojca (Mojca Miklavec)

Attachment: perl5.14.4.diff added

comment:1 Changed 10 years ago by jmroot (Joshua Root)

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.

comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: haspatch added

Changed 10 years ago by mojca (Mojca Miklavec)

Attachment: perl5.14.4.2.diff added

comment:3 Changed 10 years ago by mojca (Mojca Miklavec)

@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.

comment:4 Changed 10 years ago by mojca (Mojca Miklavec)

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)?

comment:5 Changed 10 years ago by mf2k (Frank Schima)

I don't know enough about perl to comment about #43157, but applying the version update makes sense in any event. Go for it.

comment:6 Changed 10 years ago by mf2k (Frank Schima)

Cc: mf2k@… added

Cc Me!

comment:7 Changed 10 years ago by mojca (Mojca Miklavec)

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.

comment:8 Changed 10 years ago by mojca (Mojca Miklavec)

Now that I updated 5.14, I also took the chance to update 5.12 in r119339.

comment:9 in reply to:  7 Changed 10 years ago by jmroot (Joshua Root)

Replying to mojca@…:

However I believe that a number of ports might need a revbump.

Why?

comment:10 Changed 10 years ago by mojca (Mojca Miklavec)

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.

comment:11 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:12 Changed 10 years ago by mojca (Mojca Miklavec)

Resolution: fixed
Status: newclosed

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.

Note: See TracTickets for help on using tickets.