From owner-freebsd-ports Thu Nov 14 16:23:34 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA26360 for ports-outgoing; Thu, 14 Nov 1996 16:23:34 -0800 (PST) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA26353 for ; Thu, 14 Nov 1996 16:23:32 -0800 (PST) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.2/8.7.3) with ESMTP id TAA00529; Thu, 14 Nov 1996 19:23:29 -0500 (EST) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id TAA10258; Thu, 14 Nov 1996 19:23:28 -0500 (EST) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 14 Nov 1996 19:23:28 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: Wes Santee cc: freebsd-ports@freebsd.org Subject: Re: Are these bugs? In-Reply-To: <199611142115.NAA18876@kryten.bogon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Nov 1996, Wes Santee wrote: > '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. All ports are supposed to respect ${PREFIX}, altho some don't. Usually the ones that don't are either the oldest, or some very complicated ones. I wouldn't want to be the one who has to make XFree86 respect ${PREFIX}. However, a very strong attempt to meet this is expected of every port. We'd be happy to have PRs filed on every one you notice that doesn't. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------