#725 /usr/bin/env usage
Closed: rejected a year ago Opened 2 years ago by remi.

A recent change forbids usage of /usr/bin/env in shebang (ticket #700)

Fedora project should TRUST Fedora packagers and their work. If the packager thinks it is acceptable, and wants to support it, this is his choice.

Especially, in the PHP stack, where backward compatibility is very good in new version, this is usually not a problem to use some alternative command.

Yes, user may have a broken "php" command in their path, in this case it will also break all upstream packages, usually distributed as .phar file, using /usr/bin/env shebang.

Despite same sort of issue can exists with bad libraries in the library path, RPATH usage is not used in Fedora.

Please consider reverting this change.

Of course, the rpmlint "error" should be a "warning", raising packager attention around this usage.


Ping: one month without any comment :(

Proposal, change:

env, /bin/env and /usr/bin/env MUST NOT be used. Packaged applications
cannot depend upon what the user has in their personal $PATH.

To

env, /bin/env and /usr/bin/env SHOULD NOT be used. Packaged applications
cannot depend upon what the user has in their personal $PATH. If really packager
choose to use it, this MUST be explained and default interpreter properly required.

We discussed this at this weeks meeting, given that rpm now auto fixes usage of env anyway. If you want to roll these changes back I guess you should start on fedora-devel-list and/or speak with the rpm team.

Metadata Update from @james:
- Issue close_status updated to: rejected

a year ago

Login to comment on this ticket.

Metadata