zsh-workers
 help / color / mirror / code / Atom feed
From: William Giokas <1007380@gmail.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: zsh-workers@zsh.org
Subject: Re: [wgiokas@WST420: Re: Correct installation path for completion files]
Date: Fri, 26 Jul 2013 13:41:01 -0500	[thread overview]
Message-ID: <20130726184101.GE6421@WST420> (raw)
In-Reply-To: <87d2q5goz9.fsf@ft.bewatermyfriend.org>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Fri, Jul 26, 2013 at 08:23:06PM +0200, Frank Terbeck wrote:
> William Giokas wrote:
> [...]
> > I should have made this clearer: I am looking for a generic place to use
> > in a distro-agnostic Makefile, not a specfile, PKGBUILD or ebuild. Would
> > it be sane to have the default be $datadir/zsh/site-functions, and allow
> > Debian and the select few other distros use a ./configure flag to place
> > this somewhere else?
> 
> It's hard to make it distribution-agnostic. The best way I can think of
> is to use the output of this as the destination directory:
> 
>   zsh -fc 'print ${fpath[1]}'
> 

If vendor-functions is something special that distributions use, then
they can specify that when they package this stuff. site-functions seems
to be the default for zsh, so it seems that it should be the default for
packages that install zsh completion.

Thanks,
-- 
William Giokas | KaiSforza | http://kaictl.net/
GnuPG Key: 0x73CD09CF
Fingerprint: F73F 50EF BBE2 9846 8306  E6B8 6902 06D8 73CD 09CF

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-26 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 18:07 William Giokas
2013-07-26 18:23 ` Frank Terbeck
2013-07-26 18:41   ` William Giokas [this message]
2013-07-27  0:10     ` Frank Terbeck
2013-07-27  0:10     ` Bart Schaefer

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=20130726184101.GE6421@WST420 \
    --to=1007380@gmail.com \
    --cc=ft@bewatermyfriend.org \
    --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).