blazerte wrote: > 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.
I don't buy that reasoning. Using "#!/usr/bin/perl" makes the script inflexible in that it will only work with perl in /usr/bin (unless of course you start it with "perl <scriptname>"). Using "#!/usr/bin/env perl" works just fine with perl in /usr/bin, but also works with perl in other locations. R. _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
