From owner-freebsd-ports Thu Nov 14 13:16:17 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06471 for ports-outgoing; Thu, 14 Nov 1996 13:16:17 -0800 (PST) Received: from kryten.bogon.net (kryten.bogon.net [204.137.132.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06404 for ; Thu, 14 Nov 1996 13:16:02 -0800 (PST) Received: (from wes@localhost) by kryten.bogon.net (8.7.6/8.7.3) id NAA18876 for freebsd-ports@freebsd.org; Thu, 14 Nov 1996 13:15:51 -0800 (PST) From: Wes Santee Message-Id: <199611142115.NAA18876@kryten.bogon.net> Subject: Are these bugs? To: freebsd-ports@freebsd.org Date: Thu, 14 Nov 1996 13:15:51 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 'Lo port-people. I'm trying to figure out what is the critera for what is considered a bug-free port. More specifically of the last, oh, 5 or so ports I've built, only 1 or 2 of them have actually respected the PREFIX variable to install somewhere else beside /usr/local. I realize some of the ports can't avoid it (i.e. Netscape which hard-codes /usr/local into the binary), but even emacs, which can be passed the --with-prefix=${PREFIX} flag to configure doesn't use it. If this is the way things should be, then I guess I'll go back to makefile hacking, etc.. However, if the ports should be created to respect PREFIX at least most of the time, perhaps before committing a port to the world, it should be made and installed with PREFIX pointing somewhere beside /usr/local, just to make sure the port is robust. Cheers, -- ( -Wes Santee Homepageless - and proud ) ( PGP: email w/Subject: "Send PGP Key" Powered by FreeBSD )