public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dylan Carlson <absinthe@pobox.com>
To: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Diff alternatives for etc-update
Date: Sat, 11 Jan 2003 16:29:44 -0500	[thread overview]
Message-ID: <200301111629.44793.absinthe@pobox.com> (raw)
In-Reply-To: <84hecfmmpb.fsf@lucy.cs.uni-dortmund.de>

On Saturday 11 January 2003 03:54pm, Kai Großjohann wrote:
> > I posted this in -user, but will do so again here... I believe one of
> > the easier things we can do is add support for other diff utils in
> > /etc/make.conf/.  kompare, kdiff3, gtkdiff, whatever...
>
> But it's more important to diff the right files (or versions).
> IMVHO, it's 90% which version and 10% how the diff looks.

Sure, it's important to save the user a step by diffing the most recent 
version of the config file...

...however I believe it's more important that users (some of whom are not 
regularly diffing files) can clearly see & understand what's changing.  If 
they merge incorrectly, they can screw up their system.

I say -- allow them access to tools which might make that process easier.

Making it configurable allows the user to decide the tool they want to use 
to merge, instead of us trying to make everyone happy with our sdiff 
wrapper...

sdiff's fine as a default, obviously... it works as-is, but I think 
everyone would enjoy etc-update a lot more if they had a choice of tools.  
I suspect one day we'll have a better homegrown Gentoo tool, but I don't 
see that happening in the next 6 months...

Cheers,
Dylan Carlson [absinthe@pobox.com]

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-01-11 21:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06  1:41 [gentoo-dev] etc-update & ._cfg* files: major issue with gentoo? Dhruba Bandopadhyay
2003-01-06  2:27 ` [gentoo-dev] " Brian Jackson
2003-01-06  5:24   ` Viktor Lakics
2003-01-06  6:03     ` Brian Jackson
2003-01-06 10:49     ` Jeremy Wohl
2003-01-06  6:40   ` Joseph Carter
2003-01-06  7:25 ` Kai Großjohann
2003-01-06 10:26   ` Toby Dickenson
2003-01-06 13:15     ` Thomas T. Veldhouse
2003-01-06 13:02   ` Bengt Gorden
2003-01-10 11:10     ` Kai Großjohann
2003-01-10 15:25       ` Brian Hall
2003-01-10 15:33         ` Oliver Rutherfurd
2003-01-06 15:20   ` Joseph Carter
2003-01-06  7:37 ` [gentoo-dev] " Sven Vermeulen
     [not found] ` <200301060054.29991.absinthe@pobox.com>
2003-01-10 22:38   ` [gentoo-dev] " Kai Großjohann
2003-01-10 23:05     ` William Kenworthy
2003-01-11  1:48       ` Joseph Carter
2003-01-11 10:14       ` Kai Großjohann
2003-01-11 15:19         ` [gentoo-dev] Diff alternatives for etc-update (WAS: etc-update & ._cfg* files: major issue with gentoo?) Dylan Carlson
     [not found]           ` <84hecfmmpb.fsf@lucy.cs.uni-dortmund.de>
2003-01-11 21:29             ` Dylan Carlson [this message]
2003-01-11 21:44               ` [gentoo-dev] Re: Diff alternatives for etc-update Paul de Vrieze
2003-01-11 23:59                 ` Dylan Carlson
2003-01-13 22:39           ` [gentoo-dev] Diff alternatives for etc-update (WAS: etc-update & ._cfg* files: major issue with gentoo?) Peter Ruskin
2003-01-13 22:50             ` Dylan Carlson

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=200301111629.44793.absinthe@pobox.com \
    --to=absinthe@pobox.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=kai.grossjohann@uni-duisburg.de \
    /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