public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@sympatico.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] etc-update
Date: Mon, 26 Jun 2006 14:41:23 -0400	[thread overview]
Message-ID: <20060626184123.GA4811@sympatico.ca> (raw)
In-Reply-To: <449FD4B2.2080408@verizon.net>

060626 Sean wrote:
> What is the best way to handle the files
> that etc-update states needs to be updated?

You provoked a bit of a debate (smile), but in case it's still not clear,
I've long used Etc-update with Gvim as defined in  /etc/etc-update.conf :

  # pager for use with diff commands (see NOTE_2)
  # pager="less"
  pager=""

  # diff_command="vim -d %file1 %file2"
  # diff_command="diff -uN %file1 %file2"
  # using_editor=0
  diff_command="gvim -d %file1 %file2"
  using_editor=1

  # vim-users: don't use vimdiff for merging (see NOTE_1)
  merge_command="sdiff -s -o %merged %orig %new"

Even if you're not normally a Vim user, this shows the diffs very clearly
& allows you to copy your personal changes from old to new versions.

Generally, always go through all the etc-updates & keep back-ups of  /etc .

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-06-26 18:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 12:36 [gentoo-user] etc-update Sean
2006-06-26 12:53 ` Bo Ørsted Andresen
2006-06-26 14:24   ` Alexander Skwar
2006-06-26 14:38     ` Bo Ørsted Andresen
2006-06-26 17:33       ` Alexander Skwar
2006-06-28  7:40       ` Daevid Vincent
2006-06-29 21:46         ` Tamas Sarga
2006-06-26 14:29   ` A. Khattri
2006-06-26 14:43     ` Bo Ørsted Andresen
2006-06-26 17:28       ` A. Khattri
2006-06-26 17:35         ` Bo Ørsted Andresen
2006-06-26 17:35     ` Alexander Skwar
2006-06-29 16:08       ` A. Khattri
2006-06-26 14:53   ` Daniel da Veiga
2006-06-26 15:59     ` Teresa and Dale
2006-06-26 16:29       ` Neil Bothwick
2006-06-26 17:07         ` Teresa and Dale
2006-06-26 17:30           ` A. Khattri
2006-06-26 18:17             ` Teresa and Dale
2006-06-26 23:40     ` David Corbin
2006-06-29 16:09       ` A. Khattri
2006-06-29 16:38         ` Gerhard Hoogterp
2006-06-29 17:21           ` Neil Bothwick
2006-07-02  9:43           ` Alexander Skwar
2006-06-29 21:42         ` David Corbin
2006-06-29 21:53           ` Bo Ørsted Andresen
2006-06-26 14:18 ` Alexander Skwar
2006-06-26 18:41 ` Philip Webb [this message]
2006-06-29 16:11   ` A. Khattri
2006-06-26 20:20 ` leszek

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=20060626184123.GA4811@sympatico.ca \
    --to=purslow@sympatico.ca \
    --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