Here's a quote from the Debian Python packaging manual: "If a maintainer would like to provide the user with the possibility to override the Debian Python interpreter, he may want to use /usr/bin/env python or /usr/bin/env pythonX.Y. However this is not advisable as it bypasses Debian's dependency checking and makes the package vulnerable to incomplete local installations of python."
If you substitute perl for python, I believe the same arguments would apply. IOW, while it's certainly useful for individual hackers to use /usr/bin/env, as in your case, it's not recommended as a default for Debian package maintainers for the reasons given. In my mixed testing/unstable Debian: grep -m 1 "/usr/bin/env perl" /usr/bin/* reveals only 5 files, but: grep -m 1 "/usr/bin/perl" /usr/bin/* gives 337 -- blazerte ------------------------------------------------------------------------ blazerte's Profile: http://forums.slimdevices.com/member.php?userid=5090 View this thread: http://forums.slimdevices.com/showthread.php?t=45824 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
