GNOME Bugzilla – Bug 782452
Using #!/usr/bin/perl in scripts is not portable
Last modified: 2017-05-25 18:50:24 UTC
Running 'git grep' shows several scripts in anjuta use #!/usr/bin/perl. $ git grep /usr/bin/perl libanjuta/interfaces/anjuta-idl-compiler.pl:#!/usr/bin/perl -w plugins/tools/scripts/find-fixmes.pl:#!/usr/bin/perl plugins/tools/scripts/prepare-changelog.pl:#!/usr/bin/perl -w plugins/tools/scripts/translation-status.pl:#!/usr/bin/perl po/status.pl:#!/usr/bin/perl It is better to use '#!/usr/bin/env perl' to avoid hardcoding the path to perl in scripts because some systems install perl in different places. For example, FreeBSD uses /usr/local/bin/perl by default. It used to include a /usr/bin/perl symlink for compatibility, but the symlink was removed 2 years ago. The only script I found that caused build failure on FreeBSD was plugins/tools/scripts/find-fixmes.pl. I was not sure whether the usage of #!/usr/bin/perl in other scripts can cause build problems.
I have fixed this in the master branch. The fix will be available in the next release. Thank you.