From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to work with etc-updates.
Date: Tue, 30 Aug 2005 18:22:42 +0100 [thread overview]
Message-ID: <20050830182242.04da60f6@hactar.digimed.co.uk> (raw)
In-Reply-To: <1125417989.12459.43.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Tue, 30 Aug 2005 12:06:29 -0400, Eric Crossman wrote:
> While I agree that etc-update is a vast improvement over other package
> systems, it would be nice to have a CVS type merge where I only have to
> make choices when the "system can't figure it out". It seems like
> etc-update (and friends) should be able to take advantage of mtime
> metadata and md5 checksums to determine if I've made any modifications
> to the default config file. That way an unmodified default config from
> version N can just safely be replaced with the new default for version N
> +1. Does this functionality already exist with the current etc-update?
It exists as an option with dispatch-conf, as do options to automatically
replace files if the only differences are whitespace and comments.
--
Neil Bothwick
Distrust any enterprise that requires new clothes. - Henry David Thoreau
(1817-1862)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-30 17:27 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 [this message]
2005-08-30 21:19 ` Sean Higgins
2005-08-31 9:10 ` Neil Bothwick
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=20050830182242.04da60f6@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