Charles Lane wrote:
> > When you get right down to it, perl's hosed if it's library's
> > dysfunctional, so if folks *do* mess things up we can just tell 'em "Don't
> > *do* that!"
>
> %PERL-F-DOPESLAP, logical PERL_ROOT not found, don't *DO* that!
>
> I do wonder what kind of weird situations one might run up against:
> perl embedded with libraries not used/libraries on a remote DECNET
> node that's unreachable most of the time; etc. etc. But at some
> point you have to say 'enough!'
There are a lot of people that do this practice. I even know some that
institutionalize it. Check the perl newsgroups and see all the newbie
posts about "Foo.pm not found in @INC".
I agree that having a valid PERL_ROOT is helpful (I put a lot of work
into maintaining mine) but I disagree with the -F- code enforcement.
Note that one of the reasons that rpm was rewritten in C was so that a
floppy based install did not have to have a perl binary lying around.
It'd be nice if perl could regain some of it's little portable utility
character (er, maybe :-).
Peter Prymmer
