From owner-freebsd-hackers Tue Sep 9 17:46:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20237 for hackers-outgoing; Tue, 9 Sep 1997 17:46:34 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20232 for ; Tue, 9 Sep 1997 17:46:32 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53178(5)>; Tue, 9 Sep 1997 17:45:58 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177486>; Tue, 9 Sep 1997 17:45:47 -0700 To: Lutz Albers cc: hackers@freebsd.org Subject: Re: what do you think ... should/could ports move to -> /usr/local/ports ? In-reply-to: Your message of "Mon, 08 Sep 97 01:50:58 PDT." Date: Tue, 9 Sep 1997 17:45:32 PDT From: Bill Fenner Message-Id: <97Sep9.174547pdt.177486@crevenia.parc.xerox.com> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Lutz Albers wrote: >Or use the modules system (see ). You would use the >command > module add >to add it to PATH, and > module delete >to remove it. We use something like this at PARC. It's incredibly useful, since it allows you to have multiple versions of software around and turn them on or off individually without having to rename executables, but I'm always running into hard-coded limits. My $PATH is nearly 1k bytes long, and if it gets any longer random programs start misbehaving in various strange ways. Same with $MANPATH. Bill