zsh-workers
 help / color / mirror / code / Atom feed
From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>,
	Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: The default $fpath
Date: Sun, 07 Sep 2014 22:53:02 +0300	[thread overview]
Message-ID: <1410119582.2513.51.camel@tkkaskin-mobl3.ger.corp.intel.com.tanuk.dy.fi> (raw)
In-Reply-To: <CACeGjnVjPS1nshODbb+2-8TO8GcROy5Cw66z2akd67MzWODoYw@mail.gmail.com>

On Sun, 2014-09-07 at 15:37 -0400, Vin Shelton wrote:
> On Sun, Sep 7, 2014 at 2:31 PM, Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> > The proposal is quite simply to add /usr/local/share/zsh/site-functions,
> > that and nothing else, independent of any other factors, to the default
> > fpath at some point.  I'd like to know if there are any significant
> > disadvantages to this before we even think about anything more
> > complicated.
> 
> 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. I'd be interested,
though, is /opt used exactly in the same way as /usr/local on your
system? That is, if you build a program called foo from source, do you
pass --prefix=/opt to foo's configure script, so foo's zsh completion
files will end up in /opt/share/zsh/site-functions?

My understanding is that usually /opt is used so that you'd pass
--prefix=/opt/foo to foo's configure script, so the completions will end
up in /opt/foo/share/zsh/site-functions, and there's no way zsh is going
to find them from there. So, if you use /opt, you'll anyway need to pass
some extra configure parameter when building foo, so that foo's
completion files will be installed to /usr/share/zsh/site-functions (or
whatever location you prefer). In this scheme it doesn't really matter
if you can't override the non-install-prefix-dependent zsh function
directory.

-- 
Tanu


  reply	other threads:[~2014-09-07 19:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-06 12:00 Tanu Kaskinen
2014-09-06 16:06 ` Frank Terbeck
2014-09-06 18:45 ` Peter Stephenson
2014-09-06 19:10   ` Frank Terbeck
2014-09-06 23:04     ` Peter Stephenson
2014-09-07  3:44       ` Bart Schaefer
2014-09-07 18:31         ` Peter Stephenson
2014-09-07 19:37           ` Vin Shelton
2014-09-07 19:53             ` Tanu Kaskinen [this message]
2014-09-07 20:40               ` Peter Stephenson
2014-09-07 21:01                 ` Bart Schaefer
2014-09-08 10:23                   ` Peter Stephenson
2014-09-08 11:16                     ` Frank Terbeck
2014-09-20 19:04                       ` Peter Stephenson
2014-09-20 19:36                         ` Peter Stephenson
2014-09-20 20:00                           ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1410119582.2513.51.camel@tkkaskin-mobl3.ger.corp.intel.com.tanuk.dy.fi \
    --to=tanu.kaskinen@linux.intel.com \
    --cc=acs@alumni.princeton.edu \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).