Re: [HEADS UP] perl symlinks in /usr/bin will be gone

From: Erik Trulsson (ertr1013_at_student.uu.se)
Date: 01/30/05

  • Next message: Sven Willenberger: "Re: [HEADS UP] perl symlinks in /usr/bin will be gone" 
    Date: Sun, 30 Jan 2005 16:52:01 +0100
To: Matthias Andree <matthias.andree@gmx.de>

    On Sun, Jan 30, 2005 at 02:44:38PM +0100, Matthias Andree wrote:
    > Erik Trulsson <ertr1013@student.uu.se> writes:
    >
    > >> Hardcoded paths in scripts are a mess. What if I installed Perl into
    > >> /opt/mumble on some other machine? /usr/freeware? /what/ever? Changed
    > >> $PREFIX and/or $LOCALBASE?
    > >
    > > Then you would have nobody but yourself to blame.
    >
    > So ports not heeding PREFIX or LOCALBASE aren't buggy? Interesting POV.

    That is not what I said (but, no, they are not necessarily buggy
    depending on why the they don't heed PREFIX/LOCALBASE.)
    Respecting PREFIX and LOCALBASE is good, but keeping things working is
    even better.

    >
    > > And what about all the scripts that administrators and users write that
    > > are not part of any port? Scripts that were written according to the
    > > de-facto standard that having '#!/usr/bin/perl' on the first line of
    > > the script will work correctly.
    >
    > As mentioned before, #! /usr/bin/env perl is the canonic SHORT way to
    > run perl, longer ways are in perlrun(1).

    It might be the canonic way and it might even be the best way, but it
    is not the standard way.

    Older versions of perlrun(1) (like the one included in FreeBSD 4.x)
    does not even mention /usr/bin/env so don't expect too many scripts to
    use it (and the context in which 'env' is mentioned is handling
    OS-specific limitations of the #! mechanism.)
    perlrun(1) does however say that "When possible, it's good for both
    /usr/bin/perl and /usr/local/bin/perl to be symlinks to the actual
    binary." 

    -- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@student.uu.se
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
  • Next message: Sven Willenberger: "Re: [HEADS UP] perl symlinks in /usr/bin will be gone"

    Relevant Pages

    • Re: Sample Solaris 10 SMF service provided (Was: Re: Slow file transfers on network)
      ... will never overwrite well-named user-supplied scripts. ... Sun did, but kind of th opposite to the way you are loking at it. ... I still think you can have namespace collision even within 'site' such ... that can be worked around by still tacking on a prefix within 'site'. ...
      (comp.unix.solaris)
    • Re: rc script timing issues?
      ... >> the scripts for courier run, one of the first things they do is start ... > You might be able to see this if you've installed, say, mysql-client ... > numerals to get the startup order correct. ... You'll need to prefix ...
      (freebsd-questions)
    • Re: Two questions about vim scripts
      ... I have started writing my own vim scripts and I have two questions ... The first question is about function prefixesFunctionName ... When should I prefix my function withand when should I prefix ... calling those functions from other scripts or running Vim is very hard. ...
      (comp.editors)
    • Re: wget Zielverzeichnis angeben
      ... Ich möchte aber das alle Verzeichnisse und Dateien die sich in scripts ... Set directory prefix to prefix. ...
      (de.comp.os.unix.shell)