Julian Andres Klode writes ("Bug#906901: debian-policy: Perl script shebang
requirement is disturbing and inconsistent with rest of policy"):
> In fact, we're seeing upgrade failures due to people having
> different interpreter versions in /usr/local, and there was some
> discussion about dpkg specifying a safe PATH. There was no consent
> about that, but it seems likely that APT will start specifying a
> safe PATH=/usr/sbin:/usr/bin:/sbin:/bin eventually to prevent users
> from breaking their systems.
Please do not do this.
If you absolutely must do it, make it optional.
> I agree. Let's put it this way: As a user I don't want to know whether
> the program in $PATH is a Perl script or not and then have to deal with
> local perl installations. I installed a tool, not a script, it should
> not stop working due to some unrelated change.
IMO if you install your own Perl installation in /usr/local/bin and it
doesn't work right, then you should get to keep all the resulting
pieces.
If you install a Perl installation in /usr/local/bin and it _does_
work right then there is no problem. AIUI perl XS has a reasonably
stable ABI ? At least, old modules will work with new perl binaries ?
If I wanted to install my own Perl I would make sure to have
/usr/bin/perl point to it.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
