From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: How to distribute skeleton zshrc etc. (Re: PATCH: Re: adding a toplevel zsh.spec.in file)
Date: Tue, 18 Jul 2000 08:31:15 +0000 [thread overview]
Message-ID: <1000718083115.ZM23044@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0007172256410.9316-100000@phong.blorf.net>
On Jul 17, 11:15pm, Wayne Davison wrote:
} Subject: Re: PATCH: Re: adding a toplevel zsh.spec.in file
}
} I think that RedHat/Mandrake would do well to remove all the alias,
} setopt, and similar setup that is going on in these /etc files and
} move it into the skel files that get installed for new users.
The problem with this approach is that the skel files are installed
only when a new user is created, but the package for zsh is an add-on
that can be installed or deinstalled independently. How do you update
all the users' copies of the skel files when a new version of the zsh
package is installed? How do you "distribute" skel files to existing
users when zsh is added for the first time?
You can't simply set ZDOTDIR=/etc/skel in /etc/zshenv, that would mess up
a user who has compiled his own copy of zsh (not to mention effectively
making *all* the RCs read-only). Perhaps a test in /etc/zshrc (or some
similar place that survives the latest proposed changes) for whether any
of the ~/.z{sh{env,rc},profile,login} files exists, and if none do, then
symlink them all from /etc/skel ...
Perhaps zsh should ignore the value of ZDOTDIR until after ~/.zshenv has
been sourced, but also source $ZDOTDIR/.zshenv if no ~/.zshenv exists ...
I hesitate to suggest this because it might actually break my current
personal zsh configuration, but it ought to be a little harder than it
is for a sysadmin to accidentally bypass all user-writable files. Hmm,
perhaps do the delayed-ZDOTDIR thing only for un-restricted shells?
I'm obviously thinking "out loud" here.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-18 8:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 11:53 adding a toplevel zsh.spec.in file Adam Spiers
2000-07-07 12:45 ` Peter Stephenson
2000-07-07 16:15 ` Chmouel Boudjnah
2000-07-17 14:56 ` Adam Spiers
2000-07-07 17:18 ` Bart Schaefer
2000-07-07 17:44 ` Zefram
2000-07-07 18:18 ` Bart Schaefer
2000-07-17 15:09 ` Adam Spiers
2000-07-17 17:48 ` Bart Schaefer
2000-07-17 18:07 ` Adam Spiers
2000-07-17 21:05 ` Oliver Kiddle
2000-07-17 23:35 ` Adam Spiers
2000-07-18 2:32 ` Trond Eivind Glomsrød
2000-07-18 6:01 ` Bart Schaefer
2000-07-18 1:56 ` PATCH: " Zefram
2000-07-18 5:22 ` Bart Schaefer
2000-07-18 6:15 ` Wayne Davison
2000-07-18 8:31 ` Bart Schaefer [this message]
2000-07-18 16:54 ` Trond Eivind Glomsrød
2000-07-18 6:25 ` Andrej Borsenkow
2000-07-18 9:42 ` Peter Stephenson
2000-07-18 18:22 ` Trond Eivind Glomsrød
2000-07-18 19:57 ` Zefram
2000-07-18 20:07 ` Trond Eivind Glomsrød
2000-07-18 20:37 ` Zefram
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=1000718083115.ZM23044@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).