Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jun 2002 18:10:58 -0400 (EDT)
From:      Alan Eldridge <ports@geeksrus.net>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   ports/39352: mail/p5-Mail-SpamAssassin: must delete File::Spec from base perl installation in order to install.
Message-ID:  <200206152210.g5FMAwx1005478@wwweasel.geeksrus.net>

next in thread | raw e-mail | index | archive | help

>Number:         39352
>Category:       ports
>Synopsis:       mail/p5-Mail-SpamAssassin: must delete File::Spec from base perl installation in order to install.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jun 15 15:20:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Alan Eldridge
>Release:        FreeBSD 4.6-RC i386
>Organization:
Geeksrus.NET
>Environment:
System: FreeBSD wwweasel.geeksrus.net 4.6-RC FreeBSD 4.6-RC #0: Sat Jun 15 00:38:23 EDT 2002 root@wwweasel.geeksrus.net:/usr/obj/usr/src/sys/WWWEASEL i386

>Description:

Honestly, I don't know what this should be filed under. The problem is that you
have to remove a module installed by the base system in order to do the latest
portupgrade to 2.30. The port of p5-File-Spec is 0.82, which is fine, but the
old version of File::Spec in /usr/libdata/perl gets found first and breaks the
install.

I suppose you might be able to get around it by setting PERL5LIB globally for
force searching /usr/local/lib/perl5/.... first, but I think the root of the
problem is having ports that duplicate modules in the base system... if there's
a port, then don't put it in base.

I don't know if this problem will go away once perl is exclusively a port. It
depends on whether module ports can overwrite files installed by the perl port,
and vice versa, but *only* if they are newer versions. But that's still a
nightmare, since ports doesn't handle files that are claimed by more than one
port gracefully at all at deinstall time.

Maybe the builtin @INC can be set in such a  way as to cure this problem.
Someone more perl-knowledgable than myself will need to come up with the right
solution.

>How-To-Repeat:
>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206152210.g5FMAwx1005478>