[MacPorts] #70459: exiftool @12.920.0_0+perl5_34: Can't locate Image/ExifTool.pm in @INC

[MacPorts]

#70459: exiftool @12.920.0_0+perl5_34: Can't locate Image/ExifTool.pm in @INC
-------------------------+----------------------
  Reporter:  e-maryniak  |      Owner:  dbevans
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  exiftool    |
-------------------------+----------------------

Comment (by e-maryniak):

 Replying to [comment:12 ryandesign]:
 > Replying to [comment:11 e-maryniak]:
 > > ...
 > ...
 > The question is where the fix needs to be and how far the problem
 extends. The problem seems to have been caused by an innocuous-seeming
 change of the shebang line by the exiftool authors. If the fixing of the
 shebang line occurs in the perl module build process, should it have
 caught the new one too—do we need to file a bug report with the developers
 of perl or one of its module-building modules? Or if the fix should be in
 the perl5 portgroup we can of course fix it there. But how many other
 ports that use the perl5 portgroup or this module building process are
 also using the "wrong" shebang line that isn't being replaced? How do we
 identify and fix them all? Or is it perhaps erroneous for the developers
 of exiftool to have made this change and we should ask them to change it
 back?

 To be explicit, these were the changes in the ExifTool code (ref
 [https://www.exiftool.org/history.html source history]) and all happened
 on the same day (July 24, 2024):

 **July 24, 2024 - Version 12.92**\\
 - Removed -w from exiftool shebang due to compatibility issues on some
 systems

 **July 24, 2024 - Version 12.90**\\
 - Changed exiftool shebang to use env: "#!/usr/bin/env perl -w"

-- 
Ticket URL: <https://trac.macports.org/ticket/70459#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS