From: Will Day <willday@rom.oit.gatech.edu>
To: zsh-workers@sunsite.auc.dk
Subject: Re: two sets of modules under /usr/local/lib/zsh ?
Date: Sat, 9 Sep 2000 15:44:09 -0400 [thread overview]
Message-ID: <20000909154409.A20039@rom.oit.gatech.edu> (raw)
In-Reply-To: <E13Xgu1-0007ss-00@crucigera.fysh.org>; from zefram@fysh.org on Sat, Sep 09, 2000 at 10:26:25AM +0100
[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]
A short time ago, at a computer terminal far, far away, Zefram wrote:
>>And I guess I'm wondering, if these are only for backwards compatibility,
>>(a) do I need them, if I never used paths for modules anywhere,
>
>No. In fact, they've been removed in newer versions.
>
>>Or, at the very least, have the module files in that toplevel dir all
>>hardlinked together, since they all appear to be the same file anyway.
>>Or am I missing something?
>
>Yes, either of these will work, on ELF systems. Some dynamic loading
>systems that zsh supports have requirements that mean that all module
>files have to be different (effectively, the module needs to know its
>own name).
Thanks, that definitely helps.
A short time ago, at a computer terminal far, far away, Bart Schaefer wrote:
>What do you mean by "I never used paths for modules anywhere" ?
>
>If you mean "I used modules, but never by their paths" then if you don't
>have the alias modules you'll have to change your startup files or any
>other places where you used modules, to use the zsh/modulename form.
>
>If you mean "I never used the zmodload command" then you don't need them.
Well, in my case, I had MODULE_PATH already being set in my startup files,
and so I just added the 'zsh' subdir to the path. Of course, reading your
subsequent mail, this is apparently the wrong thing to do.
>It's an attempt to be forward-looking, so that other modules that are
>not part of the zsh "package" can be distrubuted under separate module
>hierarchies, but all live under /usr/<whatever>/zsh/<version>/.
Ah, okay, well I can certainly see having separate directories for
distributed modules vs local modules. I guess the "zsh" subdir name just
seems non-intuitive; something like "main" or "dist" or "builtin" or
"standard" or something to indicate that these are modules that _come with_
zsh would be more descriptive. Calling it "zsh" when they're _all_ modules
for zsh (even the ones installed locally) is somewhat confusing. :)
Also, I'm not quite clear on why the MODULE_PATH isn't to be used like a
shell PATH, listing all the directories wherein modules may be found.
Although, if it's because dependencies are resolved by load-name, rather
than an internal name, then I can see how that would cause problems, as you
describe in your other email.
--
Will Day <PGP mail preferred> OIT / O&E / Technical Support
willday@rom.oit.gatech.edu Georgia Tech, Atlanta 30332-0715
-> Opinions expressed are mine alone and do not reflect OIT policy <-
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
Benjamin Franklin, Pennsylvania Assembly, Nov. 11, 1755
[-- Attachment #2: Type: application/pgp-signature, Size: 360 bytes --]
next prev parent reply other threads:[~2000-09-09 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-09 3:48 Will Day
2000-09-09 9:26 ` Zefram
2000-09-09 19:44 ` Will Day [this message]
2000-09-09 16:05 ` 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=20000909154409.A20039@rom.oit.gatech.edu \
--to=willday@rom.oit.gatech.edu \
--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).