Page MenuHomeFreeBSD

Add *.rc to shebangfix whitelist
ClosedPublic

Authored by AMDmi3 on Apr 19 2017, 10:36 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 16, 3:48 PM
Unknown Object (File)
Thu, Dec 5, 9:27 PM
Unknown Object (File)
Nov 6 2024, 1:47 PM
Unknown Object (File)
Nov 5 2024, 10:01 PM
Unknown Object (File)
Oct 26 2024, 6:47 AM
Unknown Object (File)
Oct 26 2024, 3:02 AM
Unknown Object (File)
Oct 3 2024, 12:14 PM
Unknown Object (File)
Oct 3 2024, 7:31 AM
Subscribers

Details

Summary

There are #!/bin/rc files installed by e.g. go:

Error: '/bin/rc' is an invalid shebang you need USES=shebangfix for 'go/src/all.rc'
Error: '/bin/rc' is an invalid shebang you need USES=shebangfix for 'go/src/clean.rc'
Error: '/bin/rc' is an invalid shebang you need USES=shebangfix for 'go/src/make.rc'
Error: '/bin/rc' is an invalid shebang you need USES=shebangfix for 'go/src/run.rc'

I'm not sure if these are usable on FreeBSD at all. We could add a shebangfix for them to use ${LOCALBASE}/bin/rc or whitelist them in qa.sh, and for now let's go the latter way.

Diff Detail

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

Event Timeline

We don't seem to have a bin/rc in our go ports, so, yeah, go ahead.

This revision is now accepted and ready to land.Apr 19 2017, 11:10 AM

There is no /bin/rc, so the warning is correct, or am I missing something?

I wonder if, instead, bin/rc should not be whitelisted.

AMDmi3 edited edge metadata.

Agreed with mat@ suggestion, whitelist /bin/rc instead

This revision now requires review to proceed.Apr 20 2017, 3:44 PM
This revision is now accepted and ready to land.Apr 20 2017, 9:57 PM

After committing this, please unfix lang/go14 :-)

This revision was automatically updated to reflect the committed changes.

Because of name collision, that change masks potential shebang error in devel/plan9port which depends on shells/rc (plan9-like shell) which provides bin/rc.
It's one obscure port, so I guess that change is ok, but it would be nice to at least add comment about this potential issue.