From owner-freebsd-questions@FreeBSD.ORG Thu Dec 11 12:53:04 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFBE916A4CE for ; Thu, 11 Dec 2003 12:53:04 -0800 (PST) Received: from zebedee.tonyjones.com (216-99-217-196.dsl.aracnet.com [216.99.217.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B6743D2B for ; Thu, 11 Dec 2003 12:53:02 -0800 (PST) (envelope-from tony@tonyjones.com) Received: by zebedee.tonyjones.com (Postfix, from userid 1000) id A31BD613; Thu, 11 Dec 2003 12:55:32 -0800 (PST) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Matthew Seaman X-Face: ZQe?G+$UQG8,i~KL=gy`T:c1bxG<{7ta&{,'$LiA !`"u>-"@wkx>yf.z_5 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Dec 2003 12:55:32 -0800 From: Tony Jones Message-Id: <20031211205532.A31BD613@zebedee.tonyjones.com> cc: paul beard cc: questions@freebsd.org Subject: Re: Perl 5.8.2 problems (was Re: how to build Spamassassin) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 20:53:04 -0000 > The main reason for doing that sort of thing with most unixoid systems > is that using a unique prefix for every software package you install > means that you can easily identify which files belong to what package > when later on it comes time to update things. I understand this, but I still like the seperation. Were I installing a package, I'd understand having to operate within the confines of someone elses location scheme, BUT I'm building from source for gods sake. Being able to change the base prefix of the port install seems like a pretty basic piece of functionality. Obviously there are some exceptions, but it would be easy for the port to inform you if PREFIX could not be changed in the environment. I did a 'make install' on portupgrade, didn't realize I'd have to install ruby to install perl :-) Grief. Then I found my problem. My stock shell was ksh, obtained from research.att.com many moons ago. It was doing some odd stuff with the environment (not via any dotted scripts). perl -v would work in ksh but once I su'd to root (csh) something was messed up. Shrug. chsh to sh or csh seems to work for that shell and also when su'ing to root. With my /usr/local/perl prefix and all. Thanks for everyones help & chastisement :-)) tony