Norbert Preining <norb...@preining.info> writes: >> If you install a Perl earlier in your PATH, you get totally >> unpredictable behavior, and everyone will be unhappy half the time.
> Well, but this is what you have asked for when you installed a Perl > earlier in your PATH. It is up to you. Unpredictable behavior, where every command written in Perl behaves randomly based on the whim of the packager? I have a hard time imagining that's what anyone is really asking for. It just doesn't seem useful. I can see the argument for consistently using /usr/bin/perl (it means that any local installation of Perl doesn't break Perl scripts from Debian packages, and they still find their dependencies through other Debian packages as intended), and for consistently using /usr/bin/env perl (the local sysadmin can interject some other version of Perl, although is now on the hook for ensuring all necessary modules are installed, following much the same logic as for not using full paths to commands in maintainer scripts). But picking one or the other essentially at random (from the perspective of the user) sounds awful. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
