From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Cc: Roman Neuhauser <neuhauser@sigpipe.cz>
Subject: Re: fndir introspection, site-packages documentation
Date: Mon, 16 Mar 2015 09:08:29 -0700 [thread overview]
Message-ID: <150316090829.ZM15335@torch.brasslantern.com> (raw)
In-Reply-To: <20150316080819.GR4524@isis.sigpipe.cz>
On Mar 16, 9:08am, Roman Neuhauser wrote:
}
} but then i'm bound to miss replies. i don't want to subscribe to
} zsh-workers (yet)...
We're pretty good about Cc'ing people when they ask to be.
Everybody, please Cc Roman.
} > Can anyone give me a situation in which an
} > oridinary user (i.e., not a software packager) would need this?
}
} how about: a site admin wants to install a function for all users.
And the site admin can't determine where to do this by simply looking
at the value of $fpath? If he's automating it for a bunch of dissimilar
platforms he's back to being a software packager.
} the behavior with *default* --prefix is, well, completely contrary
} to the intent described: "no matter how the shell was configured" is
} blatantly false thanks to this special case.
I'm leaving this to PWS as he made the changes to configure.ac. I will
however note that I think --disable-site-fndir ought to do exactly that,
and the documentation blurb is what needs fixing. If the shell is being
configured for some kind of secure/embedded environment, removing all
access to locally added functions is perfectly reasonable.
} > Maybe the right thing is to throw all of this into a module (and doc
} > for that module) that can be loaded by package maintainers
}
} zmodload or pkg-config?
I meant a zmodload module.
next prev parent reply other threads:[~2015-03-16 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150313224121.GO4524@isis.sigpipe.cz>
[not found] ` <150313203904.ZM25016@torch.brasslantern.com>
[not found] ` <20150315021436.GQ4524@isis.sigpipe.cz>
[not found] ` <150315121447.ZM27996@torch.brasslantern.com>
2015-03-16 8:08 ` Roman Neuhauser
2015-03-16 16:08 ` Bart Schaefer [this message]
2015-03-16 16:46 ` Ray Andrews
2015-03-17 15:41 ` Bart Schaefer
2015-03-17 15:55 ` Ray Andrews
2015-03-16 17:05 ` Roman Neuhauser
2015-03-17 15:45 ` Bart Schaefer
2015-03-17 16:03 ` Roman Neuhauser
2015-03-16 17:13 ` Peter Stephenson
2015-03-16 21:22 ` Roman Neuhauser
2015-03-17 15:52 ` Bart Schaefer
2015-03-17 18:46 ` Peter Stephenson
2015-03-18 3:38 ` 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=150316090829.ZM15335@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=neuhauser@sigpipe.cz \
--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).