Exactly why I use an editor, Herbert. Yes, I can read the
diff output but when the output is more than a screenful
then I'm left wondering what I missed. So I go to an
editor and have two windows. In short, it's not a no
brainer - you do have to verify what's happening to some
files that are critical such as /etc/fstab.
Unfortunately, many people don't do that. They don't
understand and bang they've killed the system. However, I
understand there is discussion and an attempt to make this
easier and a little more bulletproof <G>.
On Fri, 19 Sep 2003 21:41:30 +0200
Heribert Slama <[EMAIL PROTECTED]> wrote:
On Wed, 17 Sep 2003 08:53:43 -0400, in
gmane.linux.gentoo.user,
[EMAIL PROTECTED] wrote:
On Wed, Sep 17, 2003 at 08:33:46AM -0400, brett holcomb
wrote:
[......] I suppose you could try
an interactive update but for files like fstab I'll do
it
by hadn.
As I said, you've got to pay attention - it's not a
no-brainer.
etc-update lets you review each part of the patch and
choose to do
hand-patching on the pieces that need it. Even for files
like /etc/fstab
that require attention, it's less work (IMHO) than
pulling both old and
new versions into editors and eyeballing every one of the
changes.
Many people here say etc-update (the sdiff-stuff) is easy
- it makes
me (almost;) desparate. Hey, can't you _imagine_ that
some other
people find sdiff output _confusing_ because you see very
little of
the _context_. I need the context to feel _safe_.
So I'm forced to use an editor. I use jEdit because it
uses colors
to distinguish between different and common text. I take
the new
version as the base and re-insert my customizations. The
other way
round would be less work, but I want to have the most
recent
_comments_ in my config files.
Best regards,
-Heribert
--
Heribert Slama
Muttenz, Switzerland
--
[EMAIL PROTECTED] mailing list
--
[EMAIL PROTECTED] mailing list
