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

From: Dimitry Andric (dimitry_at_andric.com)
Date: 01/29/05

  • Next message: Phil Kernick: "Re: [HEADS UP] perl symlinks in /usr/bin will be gone" 
    Date: Sat, 29 Jan 2005 23:46:51 +0100
To: Anton Berezin <tobez@FreeBSD.org>

    On 2005-01-29 at 21:24:25 Anton Berezin wrote:

    > Unless I hear too many cries "don't do that" (with justification), I
    > plan to not create any perl symlinks in /usr/bin in the forthcoming
    > upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
    > will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
    > pollution of /usr/bin will still be performed for older versions of
    > FreeBSD, if requested via use.perl script.

    What purpose does this serve? To keep the base system clean? I'm not
    convinced that having just a few (2?) symlinks in /usr/bin will
    "pollute" the base system, but it does save having to modify
    potentially thousands of scripts. Isn't the latter *much* more
    expensive?

  • Next message: Phil Kernick: "Re: [HEADS UP] perl symlinks in /usr/bin will be gone"

    Relevant Pages

    • Re: trouble with a script
      ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ... The user input would be "domain.com", ... is how we set up a client's site on our servers. ...
      (comp.unix.shell)
    • Re: trouble with a script
      ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ... The user input would be "domain.com", ... is how we set up a client's site on our servers. ...
      (comp.unix.shell)
    • Re: trouble with a script
      ... freeBSD servers by writing a script. ... Your snippet of code doesn't look like sh on FreeBSD. ... Basically, I want my script to prompt me for two inputs, then append to ...
      (comp.unix.shell)
    • Re: Adding a -D date option to `cat
      ... and that is that it breaks compatibility. ... FreeBSD. ... If the script was written for FreeBSD and to run on FreeBSD and this is ... any reason to whine because it's not running on another Operating System. ...
      (freebsd-current)
    • Re: Bug in #! processing
      ... > No, but since this has been possible in FreeBSD for over 4.5 years, you ... >> the argument parsing done by interpreter must be different then when invoked ... immediately following it) as special comment character is bad. ... >> I don't see a convincing use for comments on the first line of script. ...
      (freebsd-current)