From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to work with etc-updates.
Date: Wed, 31 Aug 2005 10:10:29 +0100 [thread overview]
Message-ID: <20050831101029.1701ae2c@hactar.digimed.co.uk> (raw)
In-Reply-To: <200508301719.40231.sean@systura.com>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Tue, 30 Aug 2005 17:19:40 -0400, Sean Higgins wrote:
> > It exists as an option with dispatch-conf, as do options to
> > automatically replace files if the only differences are whitespace
> > and comments.
>
> But, it does not automatically do an update if the original file has
> not changed. That would be a cool feature. How often are files
> changed, for example in /etc/init.d, but you have not changed that
> file? I would love the option to automatically update any
> configuration file that I did not change from the original install.
No it does not do it automatically, that would be dangerous, You have to
enable the option first in /etc/dispatch-conf.conf
# Automerge files that the user hasn't modified
# (yes or no)
replace-unmodified=yes
--
Neil Bothwick
Guns don't kill people--it's those little pieces of lead.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-08-31 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 13:58 [gentoo-user] How to work with etc-updates Jerry Turba
2005-08-30 14:23 ` Mark Knecht
2005-09-01 0:46 ` Jerry Turba
2005-09-01 3:16 ` Mark Knecht
2005-09-01 8:09 ` Neil Bothwick
2005-10-31 17:33 ` Boyd Stephen Smith Jr.
2005-08-30 14:31 ` Roger Light
2005-08-30 14:46 ` Holly Bostick
2005-08-30 16:06 ` Eric Crossman
2005-08-30 17:15 ` Tony Davison
2005-08-30 17:22 ` Neil Bothwick
2005-08-30 21:19 ` Sean Higgins
2005-08-31 9:10 ` Neil Bothwick [this message]
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=20050831101029.1701ae2c@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox