From owner-freebsd-current Wed Jun 28 1:43:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id EFCFB37B5A9 for ; Wed, 28 Jun 2000 01:43:17 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.31.99]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FWU002I1W74AD@mta5.snfc21.pbi.net> for current@freebsd.org; Wed, 28 Jun 2000 01:42:41 -0700 (PDT) Date: Wed, 28 Jun 2000 01:43:04 -0700 From: "George W. Dinolt" Subject: Re: Bootstrapping perl ... To: Mark Murray , current@freebsd.org Message-id: <3959BA98.69D3D1E3@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en References: <39585CEA.423F53CB@pacbell.net> <200006270855.KAA55386@grimreaper.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark: Got through the buildworld with a recent cvsup. I am now running with this "world". Many thanks. I am not sure who is supposed to manage the fact that /usr/ports/Mk/bsd.ports.mk doesn't yet know about perl-5.006. One appears to need to set PERL_VER and PERL_VERSION. I just added an ."if {OSVERSION} >= 500006" , but this clearly isn't enough for people who have yet to upgrade to the newest "current'. Does this mean that the OSVERSION needs to be incremented to indicate the perl upgrade? Isn't life wonderful. Solutions to problems always lead to new problems. Regards, George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message