[Pkg-zsh-devel] Bug#934926: update

[Daniel Shahaf]

Joey Hess wrote on Sat, Jan 08, 2022 at 16:27:53 -0400:
> The simple fact is that as an upstream author who used the debian
> locations because they were the ones that worked on my system, I get bug
> reports from users of other systems that it's not right for wider uses
> of zsh. And Debian seems to be leaving it up to me to deal with it,

The right thing to do *at this time* is fairly straightforward:

- Packages that are part of Debian should install to
  /usr/share/zsh/vendor-*.

- Upstream packages have three options:

  + Install to /usr/local/share/zsh/site-functions (regardless of their
    own $PREFIX _and_ of zsh's $PREFIX)

  + Install to ${PREFIX of the zsh build}/share/zsh/site-functions

  + Install to some other place and use a post-install message to direct
    the user to amend their $fpath manually.

That's not to say that things can't be improved going forward.  Of
course they can.  I'm just trying to document the best practice at this
time.

Going forward, perhaps the vendor-* convention could be upstreamed, or
upstream could make it easier to discover its prefix, or /etc/zsh/zshrc.d/
could be added (there's a separate ticket for that but my quick grep
didn't find it), or…

Indeed, this ticket seems a bit open-ended.  What's being asked here?
Just to add /usr/share/zsh/site-functions [sic] to Debian's zsh's
default $fpath?  Or something more general, e.g., "Ensure there are as
few obstacles as possible to developers of third-party autoloadable
functions"?

Cheers,

Daniel