From owner-freebsd-current Sun Apr 2 23:43: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id A646637BB73 for ; Sun, 2 Apr 2000 23:43:04 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id CAA13542; Mon, 3 Apr 2000 02:42:41 -0400 (EDT) Message-ID: <20000403024241.A13365@netmonger.net> Date: Mon, 3 Apr 2000 02:42:41 -0400 From: Christopher Masto To: Chuck Robey , "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Perl 5.6.0? Mail-Followup-To: Chuck Robey , "Thomas T. Veldhouse" , FreeBSD-Current References: <007501bf9cec$e0b77e80$0100a8c0@veldy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Chuck Robey on Sun, Apr 02, 2000 at 05:56:22PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 05:56:22PM -0400, Chuck Robey wrote: > On Sun, 2 Apr 2000, Thomas T. Veldhouse wrote: > > > Are there any plans to merge perl-5.6.0 into current? I don't have any > > plans for using it currently, but I curious. > > Hmm. What with the nightmarish build structure of perl, I'm sure that > reading this is just going to wreck Mark's day. In light of that, and in > the absence of both any real software that needs the upgrade, and > lack of confidence in a really squeaky new release, why don't we all grant > Mark a little slack on this, at least for a while. I've been running Perl 5 since before it was included with FreeBSD, and I've never noticed anything nightmarish about the build process. I tried 5.6 a couple of days ago, and it built and tested out of the box. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message