From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12752 invoked by alias); 7 Sep 2014 20:40:25 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33126 Received: (qmail 19583 invoked from network); 7 Sep 2014 20:40:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-Originating-IP: [86.6.157.246] X-Spam: 0 X-Authority: v=2.1 cv=RdIeCjdv c=1 sm=1 tr=0 a=BvYiZ/UW0Fmn8Wufq9dPrg==:117 a=BvYiZ/UW0Fmn8Wufq9dPrg==:17 a=NLZqzBF-AAAA:8 a=AW-DWZTfyeoA:10 a=uObrxnre4hsA:10 a=kj9zAlcOel0A:10 a=QyXUC8HyAAAA:8 a=zUZ_bSqgbgYZFED4LnUA:9 a=Eks9edT-7soBMf-A:21 a=C0SH29lf-66raK7B:21 a=CjuIK1q_8ugA:10 Date: Sun, 7 Sep 2014 21:40:05 +0100 From: Peter Stephenson To: "Zsh Hackers' List" Subject: Re: The default $fpath Message-ID: <20140907214005.3190037b@pws-pc.ntlworld.com> In-Reply-To: <1410119582.2513.51.camel@tkkaskin-mobl3.ger.corp.intel.com.tanuk.dy.fi> References: <540AF773.5080407@linux.intel.com> <20140906194513.5b19931c@pws-pc.ntlworld.com> <8761h05zvt.fsf@ft.bewatermyfriend.org> <20140907000454.74cda356@pws-pc.ntlworld.com> <140906204405.ZM18404@torch.brasslantern.com> <20140907193139.3bf3d3dc@pws-pc.ntlworld.com> <1410119582.2513.51.camel@tkkaskin-mobl3.ger.corp.intel.com.tanuk.dy.fi> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 07 Sep 2014 22:53:02 +0300 Tanu Kaskinen wrote: > > I don't have a /usr/local on my system, I use /opt instead. Will it > > be possible to override the root? > > I think it's probably a good idea to make the > non-install-prefix-dependent directory configurable. No, it won't be configurable at compile time. You can already set fpath the way you want in an initialisation file. The user can override it any way they like, so there's nothing you can do to force them to use a particular path anyway. So it's already infinitely configurable by means of shell code, which is much more flexible than configuration for compilation; if you're doing that the builtin path becomes irrelevant. As the shell doesn't use the directory itself it doesn't really care at the point of installation, so there's no gain in compiling in something you can change at run time. The proposal is simply to provide a directory where there's some reasonable chance it will be found by all installations of the shell on the same system regardless of configuration. If you don't care about that particular directory because you use others, if you want to set up your own system, and in particular if you have your own custom setup files so the shell paths are how you like them, then this doesn't interest you one way or the other. In short, this is for people who *don't* want to configure the system themselves; if everyone did, the problem wouldn't have arisen. There are already plenty of ways of doing it for those who do. It is a command shell, after all. If this builtin default becomes configurable to use different directories the whole advantage is lost; it's far better to use common run-time code to ensure a non-default directory. I seem to be labouring explaining this point... I'd really like to know if there are any problems caused by *this* proposal, adding /usr/local/share/zsh/site-functions to the compiled-in path. pws