From: Tanaka Akira <akr@jaist.ac.jp>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Version-dependent functions install path
Date: 07 Jan 2000 07:23:18 +0900 [thread overview]
Message-ID: <rsqembu4z6x.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Peter Stephenson's message of "Thu, 06 Jan 2000 20:20:54 +0000"
In article <E126JN1-0003cR-00.2000-01-06-20-18-55@mail2.svr.pol.co.uk>,
Peter Stephenson <pws@pwstephenson.fsnet.co.uk> writes:
> I hope the choice of path (default
> `/usr/local/share/zsh/functions/3.1.6-dev-14', mutatis mutandis) is
> rational. The version-specific bit comes last, as with the module path,
> and the `share' remains present, despite the version-dependence, because it
> refers to the absence of machine-dependence (it worried me at first, but
> actually I've just noticed Emacs does exactly the same with its lisp code).
> Indeed, this will make it easier to share functions across architectures
> potentially running different versions of the shell.
I think DATADIR/zsh/VERSION/functions is better than
DATADIR/zsh/functions/VERSION because it enables us to collect version
specific stuff other than functions. Also when a lazy administrater
install zsh-3.1.7 over zsh-3.1.6, a directory structure stays somewhat
clean.
Also, DATADIR/zsh/VERSION/site-functions and
DATADIR/zsh/site-functions should be exist for site specific
modifications and add-on packages. Currently there is no add-on
packages, though.
--
Tanaka Akira
next prev parent reply other threads:[~2000-01-06 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 7:04 Andrej Borsenkow
2000-01-06 8:06 ` dev-14 problem - can't load zsh/complete " Andrej Borsenkow
2000-01-06 10:50 ` Oliver Kiddle
2000-01-06 20:20 ` Peter Stephenson
2000-01-06 22:23 ` Tanaka Akira [this message]
2000-01-07 22:26 ` Peter Stephenson
2000-01-09 2:58 ` Tanaka Akira
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=rsqembu4z6x.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--cc=zsh-workers@sunsite.auc.dk \
/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).