New system build overwrites perl modules?
Anton Berezin
tobez at tobez.org
Mon May 19 09:53:10 PDT 2003
On Mon, May 19, 2003 at 08:33:00AM -0700, randall s. ehren wrote:
> > On Mon, May 19, 2003 at 01:12:16AM -0400, Forrest Aldrich wrote:
> > > I've had a problem with 4.8-STABLE whereby a new system build/install
> > > appears to nudge out the module File::Spec (perhaps others), which I
> > > usually have to reinstall every time. I'm curious about what's
> > > happening here, why, etc.
> >
> > Do you install File::Spec from ports?
> > Do you use lang/perl5 port?
>
> same thing happened to me, i installed File::Spec from CPAN, which hasn't
> been a problem in previous upgrades.
Well.
If you were to use perl port and install File::Spec from CPAN, you'd be
safe.
If you were to use base system perl and install File::Spec from the
ports (devel/p5-File-Spec), you'd be safe.
Needless to say, you'd be safe to use both perl port and File::Spec from
the ports.
As it is now, base system perl does not provide the protection from the
modules which insist on setting INSTALLDIRS => 'perl' in their
Makefile.PL. If you use the port, this protection is provided by the
ports maintainer. If you use perl from ports, this protection is
provided by BSDPAN, which is not present in the base system perl.
Apart from the two workarounds I mentioned, the third one is to set
NOPERL=yes in your /etc/make.conf, so that buildworld/installworld
process will not overwrite existing perl installation.
Cheers,
\Anton.
--
You shouldn't be intimidated by this issue at all, since Perl is your
friend. -- Apache mod_perl guide
More information about the freebsd-stable
mailing list