Date: Sun, 10 Dec 2000 14:18:51 -0500 From: Brian Dean <bsd@bsdhome.com> To: Mike Meyer <mwm@mired.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Package installation location Message-ID: <20001210141851.C39643@vger.bsdhome.com> In-Reply-To: <14899.54065.737498.114689@guru.mired.org>; from mwm@mired.org on Sun, Dec 10, 2000 at 01:02:09PM -0600 References: <20001210125026.A27718@drama.navipath.com> <xzpitosgn0w.fsf@flood.ping.uio.no> <20001210132152.B27718@drama.navipath.com> <14899.54065.737498.114689@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 10, 2000 at 01:02:09PM -0600, Mike Meyer wrote: > The problem is that *it doesn't work*. Well, not very well. Part of it > is that it's only given lip service: the porters handbook says "make > your ports PREFIX clean"; portlint doesn't do any checking about it. > The porters handbook doesn't even provide instructions on how to test > for whether or not a port is PREFIX clean. Making things LOCALBASE > clean isn't even suggested. Just to nitpick this one statement, PREFIX is set to LOCALBASE (see /usr/ports/Mk/bsd.port.mk) so if PREFIX is honoured by the port, then LOCALBASE will be honoured by default. Not doing it this way would not allow you to override PREFIX for one particular port. Thus if you set LOCALBASE to /usr/opt in /etc/make.conf for instance, but for port "foo" you want it to go somewhere else, you can build that with make PREFIX=/usr/local/foo, for instance. If foo honoured LOCALBASE instead, it would ignore your one-time PREFIX override. Thus PREFIX is the correct thing for the ports to worry about, not LOCALBASE, LOCALBASE just being the default value for PREFIX. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001210141851.C39643>