zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayned@users.sourceforge.net>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: Zsh Workers <zsh-workers@sunsite.dk>, <cooker@linux-mandrake.com>
Subject: Re: Mandrake 8.0 - compinit in /etc/zshrc
Date: Mon, 21 May 2001 11:17:18 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.33L2.0105211106540.1399-100000@phong.blorf.net> (raw)
In-Reply-To: <m31ypi3guy.fsf@giants.mandrakesoft.com>

On 21 May 2001, Chmouel Boudjnah wrote:
> and how do you do when you have to modify the skel file on upgrade ?

Here's an alternate solution.  See if you like this.

For a package such as zsh, create a patch in the source rpm that adds
an extra rc-file check that works like this:  If the user's rc file is
missing, we read the default rc file from /usr/lib/zsh (or similar).
This gives all users the default "power options" up until they decide to
take their fate into their own hands and create their own rc file, at
which time they are responsible for updating it on upgrade.  The only
downside I see in this is that the user needs to be made aware that when
they create their own rc file, that they may wish to copy the default rc
file and modify that rather than starting from scratch.  Do you think
that is too big of a problem?  (I don't consider the fact that a user
that creates their own rc file may need to edit their rc file on upgrade
a problem since these users already have to deal with changing their rc
file on upgrade in the current scheme to handle interactions between the
new system rc and their old home rc file).

..wayne..


  parent reply	other threads:[~2001-05-21 18:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-19 18:19 Andrej Borsenkow
2001-05-19 20:26 ` Bart Schaefer
2001-05-19 21:51   ` Wayne Davison
2001-05-20  8:11     ` Andrej Borsenkow
2001-05-20  9:10       ` Wayne Davison
2001-05-21 14:40         ` Chmouel Boudjnah
2001-05-21 14:29           ` Clint Adams
2001-05-21 15:37             ` Chmouel Boudjnah
2001-05-21 15:15               ` Clint Adams
2001-05-21 17:06                 ` Oliver Kiddle
2001-05-21 17:12                 ` Chmouel Boudjnah
2001-05-21 17:24                   ` Andrej Borsenkow
2001-05-21 18:27                     ` Chmouel Boudjnah
2001-05-21 15:50           ` Bart Schaefer
2001-05-21 18:17           ` Wayne Davison [this message]
2001-05-21 18:29             ` Andrej Borsenkow
2001-05-21 19:07             ` Bart Schaefer
2001-05-21 19:21             ` Chmouel Boudjnah
2001-05-21 10:54       ` [Cooker] " Chmouel Boudjnah
2001-05-20 18:26     ` Trond Eivind Glomsrød

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=Pine.LNX.4.33L2.0105211106540.1399-100000@phong.blorf.net \
    --to=wayned@users.sourceforge.net \
    --cc=chmouel@mandrakesoft.com \
    --cc=cooker@linux-mandrake.com \
    --cc=zsh-workers@sunsite.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).