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), gentoo-dev@gentoo.org
Subject: [gentoo-dev] Diff alternatives for etc-update (WAS: etc-update & ._cfg* files: major issue with gentoo?)
Date: Sat, 11 Jan 2003 10:19:34 -0500	[thread overview]
Message-ID: <200301111019.34624.absinthe@pobox.com> (raw)
In-Reply-To: <84d6n49en7.fsf@lucy.cs.uni-dortmund.de>

On Saturday 11 January 2003 05:14am, Kai Großjohann wrote:
>
> (I agree with the other posters that diff3 is even /more/ useful, but
> that's easy to add once the right version (A) is available.)

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...

It's faster & easier to parse things (particularly large files) accurately 
with a GUI diff util.  kdiff3 also allows you to type into the merge file 
freeform (in case you want to make a few more manual changes not in either 
file being diffed).

/etc/make.conf examples:

DIFFCOMMAND=/usr/bin/kdiff3 ${FILE1} ${FILE2} ${FILE3} -o ${MERGEFILE}

DIFFCOMMAND=/usr/bin/gtkdiff ${FILE1} ${FILE2} ${FILE3} -o ${MERGEFILE}

DIFFCOMMAND=cp ${FILE1} ${MERGEFILE} && /usr/bin/kde/3.1/bin/kompare 
${MERGEFILE} ${FILE2}

// Kompare doesn't have an -o option... it merges changes back into the
// first file specified on the commandline.  or the changes can be saved as
// a .diff file.

Ebuilds?  Yes.

* gtkdiff is in app-misc/gtkdiff
* kdiff3 is in dev-util/kdiff3
* kompare is part of kde-base/kdesdk

Cheers,
Dylan Carlson [absinthe@pobox.com]

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-11 15:22 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         ` Dylan Carlson [this message]
     [not found]           ` <84hecfmmpb.fsf@lucy.cs.uni-dortmund.de>
2003-01-11 21:29             ` [gentoo-dev] Re: Diff alternatives for etc-update Dylan Carlson
2003-01-11 21:44               ` 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=200301111019.34624.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