From owner-freebsd-perl@FreeBSD.ORG Thu Jan 29 18:36:17 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 B145116A4CF for ; Thu, 29 Jan 2004 18:36:17 -0800 (PST) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85D9043D5E for ; Thu, 29 Jan 2004 18:36:09 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.160.236.34]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040130023608.EONJ25581.out001.verizon.net@mac.com> for ; Thu, 29 Jan 2004 20:36:08 -0600 Message-ID: <4019C2F6.1000403@mac.com> Date: Thu, 29 Jan 2004 21:35:34 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-perl@FreeBSD.org References: <1075425257.93790.21.camel@gorf.lovett.com> In-Reply-To: <1075425257.93790.21.camel@gorf.lovett.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.160.236.34] at Thu, 29 Jan 2004 20:36:08 -0600 Subject: Re: Certain perl ports overlapping with perl-5.8.2 install X-BeenThere: freebsd-perl@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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 02:36:17 -0000 Ade Lovett wrote: [ ... ] > This is a pretty disgusting hack, so I'm soliciting comments as to the > right way to do this. Would it be acceptable for the p5- ports (and Mail::SpamAssassin :-) to invoke CPAN/BSDPAN as appropriate and generate a pkg-plist from the install results? After all, Perl already tests new modules before installing them using that mechanism, which appears to be more likely to catch any problems than what is currently being done with some of the Perl ports... -- -Chuck