Re: help with grep looking for cats and dogs

In article <008301c62419$5f7eb6c0$6800000a@venti>,
Brian K. White <brian@xxxxxxxxx> wrote:

[Lucretia Deletia hacks away most of the text here - wjv]

>..

>I find it amusing reading such things as a post to a zsh mail
>list recently where the guy "discovered" that it's non-trivially
>worth while to do things with shell built-ins that he and most
>others would commonly do with perl one-liners. And of course
>it's old news by now how freebsd re-wrote a ton of scripts and
>stripped all perl out of it's base system. That probably had
>less to do with performance than removing a big package and
>also making it easier for people to use the latest version from
>ports without complications and conflicts with the older base os
>version.

Actually perl is still in the base system. What was changed were
the perl scripts needed to install and/or compile and install
a system.

The only reason was to get the ever changing and always larger
Perl out of the install process system so that it would be far easier
to put in such small dedicated appliance like devices.. It took them quite
a while to rewrite all the Base OS scripts to elinate them and replace with
shell scripts. There is still a perl in the base OS but you don't
need one for system makes and installs.

It elminted such problems encounted from moving from 3.x to 4.x
by building sources [as opposed to a binary upgrade].

That required a define -DNOPERL and then building world, then
building and installing a kernel, then going back and build install
and reboot a couple of more times.

This was the culmination of a major streamling when they moved
disk naming conventions, got rid of block devices, and a few other
things. The 4.0 to 4.x required a couple of steps but since then
it's clean.

There is a Perl in the base system but now it's not needed for
building a system. And it's easy to switch from the base perl - in
the full OS - to a port perl. It's a short CLI command that tell
the OS which port to use.

I've had to go back to the base system for some ports when making
and/or installing them, but then just switch back after the
install. I honestly don't recall what it was that required that.

Bill


--
Bill Vermillion - bv @ wjv . com
.

Relevant Pages

  • Re: how to build Spamassassin
    ... The ports collection is great for certain things. ... it for spam assassin on 4.9 Stable. ... Install Perl 5.8.2 from ports ... Install Spam assassin from ports ...
    (freebsd-questions)
  • Re: mod_perl HELP!
    ... >> Don't link stuff like perl unless you know what you are doing. ... That takes a while with over 200 ports. ... or you had it when you tried to install mod_perl? ... > instead of bsdpan modules to replace them and if so how to remove the ...
    (freebsd-questions)
  • RE: /libexec/ld-elf.so.1: Shared object "libssl.so.3" not found
    ... Both that, and pkg_add are standard parts of the base system, although ... tools suite in the ports system. ... you shouldn't install a port that duplicates part of the ... you're installing provides shared libraries. ...
    (freebsd-questions)
  • Re: Updating Ports Index
    ... I installed perl, so I'm no longer getting the 'perl: ... >Subject: Updating Ports Index ... >For some reason, I can't seem to update the index for the ports database: ... >was a minimal install, do I need to install something else for the 'make ...
    (freebsd-questions)
  • Re: upgrading perl
    ... If you want to switch to the ports version of perl, ... You can also install all the CPAN modules using the base system, ...
    (freebsd-questions)