bug or feature: env perl -w

[Alessandro Rubini]

> echo "#!/usr/bin/env perl -w" > envperlw

The bang line can only list a command and a single argument.

So here the argument to env is "perl -w". Like this:

tornado% env "perl -w"
env: perl -w: No such file or directory

Like yours:

> env: perl -w: No such file or directory


> Sounds like a bug to me...

I don't understand. Who is the buggy program?

As for glib-mkenums I get this:

tornado% head -1 /usr/bin/glib-mkenums
#!/usr/bin/perl -w

Which is perfectly fine.

Why do you need env? is because your perl is installed in a
non-standard place but is reachable through the path?  If so, I think
you should set the -w option in the code, like "use warnings".

/alessandro