[MacPorts] #70459: exiftool @12.920.0_0+perl5_34: Can't locate Image/ExifTool.pm in @INC
MacPorts
noreply at macports.org
Mon Jul 29 17:29:24 UTC 2024
#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 ryandesign):
Replying to [comment:11 e-maryniak]:
> Indeed `#!/usr/bin/env perl5` is what the current installation of
exiftool does:
>
>
> {{{
> $ sudo port uninstall exiftool
> ---> Deactivating exiftool @12.920.0_0+perl5_34
> ---> Cleaning exiftool
> ---> Uninstalling exiftool @12.920.0_0+perl5_34
> ---> Cleaning exiftool
> $ sudo port install exiftool
> ---> Computing dependencies for exiftool
> ---> Fetching archive for exiftool
> ---> Attempting to fetch
exiftool-12.920.0_0+perl5_34.darwin_any.noarch.tbz2 from
https://packages.macports.org/exiftool
> ---> Attempting to fetch
exiftool-12.920.0_0+perl5_34.darwin_any.noarch.tbz2.rmd160 from
https://packages.macports.org/exiftool
> ---> Installing exiftool @12.920.0_0+perl5_34
> ---> Activating exiftool @12.920.0_0+perl5_34
> ---> Cleaning exiftool
> ---> Scanning binaries for linking errors
> ---> No broken files found.
> ---> No broken ports found.
> $ head -n 1 /opt/local/bin/exiftool
> #!/usr/bin/env perl5
> $_
> }}}
Uninstalling and reinstalling the exiftool port doesn't prove anything in
that regard since the exiftool port only installs the
/opt/local/bin/exiftool symlink. The script it points to,
/opt/local/libexec/perl5.34/exiftool, is installed by the p5.34-image-
exiftool port. Uninstalling and reinstalling that port would prove what
that file contains right after installation.
> Looking forward to a more permanent solution which, if I understand you
well, should not be too difficult (a fixed `reinplace` or "after-fix-
reinplace` when the CPAN build has completed).
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?
--
Ticket URL: <https://trac.macports.org/ticket/70459#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list