zsh-workers
 help / color / mirror / code / Atom feed
From: zeurkous@blaatscaahp.org
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org, Wu Zhenyu <wuzhenyu@ustc.edu>
Subject: install paths (was: Re: [feature] Provide a pkg-config file)
Date: Sat, 15 Jul 2023 10:28:25 +0000 (UTC)	[thread overview]
Message-ID: <thinkcrap!zeurkous!1689416903.15295@uucp.> (raw)
In-Reply-To: <30426-1689385954.869850@Ch1l.hz71.QZ_I>

On Sat, 15 Jul 2023 03:52:34 +0200, Oliver Kiddle <opk@zsh.org> wrote:
> It may be the case that this causes completion functions to
> be installed in a directory that isn't in zsh's default $fpath but
> that's the responsibility of the system administrator to configure.

Me's long been in favour of a general PREFICES variable to replace (or,
probably more realistically: amend) the various *PATH vars (and, in this
case: the fpath var).

In fact, on me machines, me even initializes the *PATH variables from
that var (it's also necessary to have a SUFFICES var 'cause of exisiting
{{,s}bin,libexec,...} divergence). Me's only been using site-functions
relatively recently, but me should then initialize the fpath var from
the PREFICES one as well -- thanks for pointing this out.

> Software dumping files outside of it's designated installation prefix is
> something that should be avoided.

Keep in mind though, that there appear to be some general (but not
universal!) exceptions, such as /{etc,var}/.

And then, as a "driving it too far" example, there's the horrible lunix
/opt/...

        --zeurkous.

-- 
Friggin' Machines!


      reply	other threads:[~2023-07-15 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 17:34 [feature] Provide a pkg-config file Wu Zhenyu
2023-07-14 18:08 ` Johan Grande
2023-07-15  1:52 ` Oliver Kiddle
2023-07-15 10:28   ` zeurkous [this message]

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='thinkcrap'\!'zeurkous'\!'1689416903.15295@uucp.' \
    --to=zeurkous@blaatscaahp.org \
    --cc=opk@zsh.org \
    --cc=wuzhenyu@ustc.edu \
    --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).