From owner-freebsd-stable Sun Sep 13 10:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28302 for freebsd-stable-outgoing; Sun, 13 Sep 1998 10:48:08 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28274; Sun, 13 Sep 1998 10:48:04 -0700 (PDT) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 0zIGFa-0001rN-00; Sun, 13 Sep 1998 10:47:50 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id KAA28410; Sun, 13 Sep 1998 10:47:41 -0700 Date: Sun, 13 Sep 1998 10:47:41 -0700 (PDT) Reply-To: patl@phoenix.volant.org Subject: Re: Perl version in FreeBSD To: Mark Murray cc: patl@phoenix.volant.org, Dean Hollister , stable@FreeBSD.ORG, FreeBSD Questions In-Reply-To: <199809131733.TAA16884@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 1. Perl5 is not 100% backwards compatible with perl4. It is > > quite possible that some perl4 scripts will fail if executed > > by perl5. > > True. Easy to fix. Done on FreeBSD-CURRENT. Yes, but you have to -find- them all to fix them. The worry wasn't so much about scripts in the distribution, or even ones in the ports and packages collections, so much as whatever other scripts might be in use at customer sites. (Think, for example, CGI scripts...) A minor release, especially a dot-dot release, shouldn't break anything unless it is absolutely necessary to properly fix something more important. That's why the switch to perl5 (and bind 8, and...) was delayed until (well) after -current switched from 2.x to 3.0; and why it will not happen in -stable until that branch also moves to 3.x. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message