zsh-workers
 help / color / mirror / code / Atom feed
From: Will Day <willday@rom.oit.gatech.edu>
To: zsh-workers@sunsite.auc.dk
Subject: two sets of modules under /usr/local/lib/zsh ?
Date: Fri, 8 Sep 2000 23:48:50 -0400	[thread overview]
Message-ID: <20000908234850.A16212@rom.oit.gatech.edu> (raw)

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

Okay, I haven't been keeping up with the list since 3.1.6, so this may be a
stupid question, but why are there two sets of modules under
/usr/local/lib/zsh?  There seems to be a set under 3.1.9, and then another,
larger, set under 3.1.9/zsh.

Looking through the NEWS and the mailing list archives, I see the modules
were moved from the version dir to the zsh subdir, and the ones in the top
directory are apparently called "alias modules".  However, what really
baffles me, is that they all appear to be the same file:

   % cd /usr/local/zsh/3.1.9
   % sum *.so
   33949     5 cap.so
   33949     5 clone.so
   33949     5 compctl.so
   33949     5 complete.so
   ...

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, and (b) if
say I do want them, could they not instead be just symlinks to the
respective module under the zsh subdir?  Ie:

   % cd /usr/local/zsh/3.1.9
   % ls -l *.so
   lrwxrwxrwx   1 root   other   10 Sep  8 23:39 cap.so -> zsh/cap.so
   lrwxrwxrwx   1 root   other   10 Sep  8 23:39 clone.so -> zsh/clone.so
   lrwxrwxrwx   1 root   other   10 Sep  8 23:39 compctl.so -> zsh/compctl.so
   lrwxrwxrwx   1 root   other   10 Sep  8 23:39 complete.so -> zsh/complete.so

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?

I probably wouldn't ever notice or care, except that I'm building a Solaris
pkg to install across all our machines, and the prototype file gets a bit
confusing with two of every module in there.  If I can make them symlinks,
or hardlinks, it'll make it all cleaner and easier to deal with. :)

Also, I guess I'm a little curious about it all, since the new path:
   /usr/local/zsh/3.1.9/zsh/cap.so

seems a little unnecessarily redundant, with two "zsh"'s in there.

-- 
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 --]

             reply	other threads:[~2000-09-09  3:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-09  3:48 Will Day [this message]
2000-09-09  9:26 ` Zefram
2000-09-09 19:44   ` Will Day
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=20000908234850.A16212@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).