From owner-freebsd-current Tue May 7 16: 2:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 0378937B40A for ; Tue, 7 May 2002 16:02:21 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1920) id DAF75AE03F; Tue, 7 May 2002 16:02:16 -0700 (PDT) Date: Tue, 7 May 2002 16:02:16 -0700 From: Maxime Henrion To: current@FreeBSD.org Cc: Mark Murray Subject: Re: The future of perl on FreeBSD Message-ID: <20020507230216.GQ63621@elvis.mu.org> References: <200205072241.g47Mf0jV002339@grimreaper.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205072241.g47Mf0jV002339@grimreaper.grondar.org> User-Agent: Mutt/1.3.27i 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 Mark Murray wrote: [long explanation and other solutions ripped] > 3) Ditch perl from the base system completely, and rely on the > ports system for FreeBSD's perl requirements. > 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. > I've tested a build of this, including kernel. Some apps > (like sockstat) break. I could commit this if it is wanted. Another possibility is to ditch perl from the base system and making it a port, but still installing the port by default. This solves the only "CON" for this solution. As already pointed out by desand brooks, this is how Debian and Solaris are doing. Given that the Perl community expressed no problems regarding the way Perl is distributed on these two OS's as far as I know, we can probably assume that this solution will also please the Perl community. Thanks, Maxime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message