From owner-freebsd-perl@FreeBSD.ORG Wed Aug 11 20:02:58 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 B458C16A4CF; Wed, 11 Aug 2004 20:02:58 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id A496C43D31; Wed, 11 Aug 2004 20:02:58 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from ts46-02-qdr1249.mdfrd.or.charter.com ([66.169.242.225] helo=[192.168.1.101]) by mail.lovett.com with asmtp (Exim 4.41 (FreeBSD)) id 1BuzJK-0004zP-I5; Wed, 11 Aug 2004 20:02:58 +0000 In-Reply-To: <411A5763.80702@FreeBSD.org> References: <411A46DA.6030600@iis.sinica.edu.tw> <411A5763.80702@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <70CEDA91-EBD1-11D8-8E5E-000A956B6386@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Ade Lovett Date: Wed, 11 Aug 2004 13:02:58 -0700 To: Sergey Skvortsov X-Mailer: Apple Mail (2.619) cc: freebsd-perl@freebsd.org Subject: Re: PERL_LEVEL conditional dependencies 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: Wed, 11 Aug 2004 20:02:58 -0000 On Aug 11, 2004, at 10:29, Sergey Skvortsov wrote: > I think your patch for p5-File-Temp: > > .if ${PERL_LEVEL} > 500800 > IGNORE= "This module is already included in perl 5.8.x and later." > .endif > > is senseless and detrimental. Ok, let's slow down a bit here. This is obviously an issue that is likely to cause much consternation (I'm specifically avoiding use of the "b-word" here :) > All p5-ports with IGNORE like "This module is already included in perl > X.Y.Z" should be cleaned up. Well, the standard answer to that would be "patches welcome", but is not particularly useful at this point. Going forward, I would *strongly* recommend that all the perl hooks etc. be pulled out into a Mk/bsd.perl.mk -- this is an absolute requirement if further work is to be done on the ports infrastructure as it relates to perl, since we don't want to be tied into the primary bsd.port.mk. Once the first "null-commit" has happened (bsd.port.mk -> bsd.port.mk/bsd.perl.mk) then, and only then, will it make sense to start working on a (new/improved/better/whatever) perl port infrastructure. Initial testing can be thrown around by adding to bsd.perl.mk in the presence of a specific all-encompassing-variable (eg: USE_PERL_NEW_WORLD_ORDER=YES :) so that regular end-user consumers of the perl ports won't see *any* changes until the switch is flipped. Then, and only then, will it be possible to sit down, write up what works, and what doesn't, with the current system, create a wishlist, and then get down to the coding work, handing out a few more PhD's in make(1) operation :) Having recently done the work to extract GNU autotools from bsd.port.mk into its own standalone file, and being a big consumer of perl ports myself, I'm certainly willing to offer my services in getting a bsd.perl.mk set up. -aDe