Page MenuHomeFreeBSD

Mk/Uses/shebangfix.mk: Fix SHEBANG_FILES to use find(1)
ClosedPublic

Authored by feld on Aug 3 2017, 7:16 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 7, 7:12 PM
Unknown Object (File)
Sun, Oct 5, 4:31 AM
Unknown Object (File)
Thu, Oct 2, 1:14 AM
Unknown Object (File)
Wed, Oct 1, 4:10 PM
Unknown Object (File)
Wed, Oct 1, 10:58 AM
Unknown Object (File)
Sep 10 2025, 1:44 PM
Unknown Object (File)
Sep 6 2025, 4:34 AM
Unknown Object (File)
Sep 4 2025, 10:35 PM
Subscribers
None

Details

Summary

Ports like net/vmware-vsphere-cli use SHEBANG_FILES with globs like so:

SHEBANG_FILES= bin/* ...

As of FreeBSD 11.??? sed has changed and errors if attempted on non-file objects. In
the case of the cited port there are many other files in the bin/
directory which are symlinks for compatibility with old scripts. This
causes the port patching to fail.

Changing the SHEBANG_FILES logic to use find(1) like SHEBANG_REGEX and
SHEBANG_GLOB seems to be a sane solution with no negative impact.

Test Plan

exp-run?

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This looks like a good idea. An exp-run may be needed though, there are strange things happening in SHEBANG_FILES.

This revision was automatically updated to reflect the committed changes.