From owner-freebsd-current Tue May 7 16:22: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from devonshire.cnchost.com (devonshire.concentric.net [207.155.248.12]) by hub.freebsd.org (Postfix) with ESMTP id 6548537B408 for ; Tue, 7 May 2002 16:21:56 -0700 (PDT) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by devonshire.cnchost.com id TAA13894; Tue, 7 May 2002 19:21:46 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200205072321.TAA13894@devonshire.cnchost.com> To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: The future of perl on FreeBSD In-reply-to: Your message of "Tue, 07 May 2002 23:41:00 BST." <200205072241.g47Mf0jV002339@grimreaper.grondar.org> Date: Tue, 07 May 2002 16:21:45 -0700 From: Bakul Shah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > 3) Ditch perl from the base system completely, and rely on the > ports system for FreeBSD's perl requirements. YESSSSS!!!! > PRO: Speed up "make world", debloat source tree, prevent > many cross-build breakages. > CON: No high-level scripting system in the tree by default > (need to install a port to get one). The ports collection > will need some work to handle this. The base system should be able to get by with sh/awk/sed like it did before the Perl camel entered the tent. If - the core system was much smaller, - there was a much tigher integration with ports, and - there was a way to easily select which system configuration *profile* you wanted to install or modify before installing, a wide variety of users may be made happy. But this is a separate & often repeated discussion, I guess! -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message