From owner-freebsd-perl@FreeBSD.ORG Thu Jan 29 17:13:47 2004 Return-Path: Delivered-To: freebsd-perl@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 269A016A4CE; Thu, 29 Jan 2004 17:13:47 -0800 (PST) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B65643D1F; Thu, 29 Jan 2004 17:13:46 -0800 (PST) (envelope-from ade@FreeBSD.org) Received: from ts46-02-qdr1249.mdfrd.or.charter.com ([66.169.242.225] helo=[192.168.1.2]) by mail.lovett.com with asmtp (Exim 4.30; FreeBSD) id 1AmNEA-000JI1-3P; Fri, 30 Jan 2004 01:13:46 +0000 From: Ade Lovett To: freebsd-perl@FreeBSD.org Content-Type: text/plain Message-Id: <1075425257.93790.21.camel@gorf.lovett.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 29 Jan 2004 17:14:17 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-ports@FreeBSD.org Subject: Certain perl ports overlapping with perl-5.8.2 install X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-perl@FreeBSD.org List-Id: maintainer of a number of perl-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 01:13:47 -0000 [Admin note: sent to perl@ and ports@ to hit a slightly wider audience initially - replies to perl@ only please] With my dinkering around with perl5.8.2, I've run into something of a problem. A number of ports, so far I have found: converters/p5-MIME-Base64 devel/p5-Storable devel/p5-Test-Harness devel/p5-Test-Simple devel/p5-Time-HiRes net/p5-Net security/p5-Digest-MD5 are also part of the lang/perl5.8 port. Some of the ports are newer than those in perl5.8, others are the same, still others are older. However, what this does mean, that the following sequence: cd ${PORTSDIR}/lang/perl5.8; make install cd ${PORTSDIR}/{one-of-the-ports-above}; make install deinstall will end up removing parts of lang/perl5.8 port, resulting in much hilarity. With our local ports tree, I've simply added code to these ports to tag them as BROKEN for appropriate PERL_VERSION value, and then start the slow slog through the rest of the ports/packages we build to adjust dependencies accordingly, when a port tries to bring in one of these "troublemakers" as a dependency. This is a pretty disgusting hack, so I'm soliciting comments as to the right way to do this. -aDe