From: "Trenton Adams" <trenton.d.adams@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: etc-update vs dispatch-conf
Date: Fri, 13 Oct 2006 23:21:18 -0600 [thread overview]
Message-ID: <9b1675090610132221t1a76535dl2ae9fbe7fdd58292@mail.gmail.com> (raw)
In-Reply-To: <4df051c10610131530l7a5f06aflfeaeaedc4e9c599a@mail.gmail.com>
I use dispatch-conf all the time. I too have never looked back.
I use diff="vimdiff -R %s %s" in /etc/dispatch-conf.conf
NOT SURE WHAT '-R' IS now though. Perhaps it should not be there.
Then I add the following line to my .vimrc, which allows me to press
F2 to exit the vimdiff windows in one shot.
map <F2> <Esc>:q<CR><Esc>:q<CR>
The old config shows up on the left, and the new config shows up on the right.
Press Ctrl-W and the left or right arrow key to switch between window buffers.
What I usually do, if there are additions to the new config that I
want, is copy them from the right window, paste them in the left
window, and save the left window. Then, I hit F2, then 'z' for zap,
and my old config has the new settings that it needs.
If you don't like vim, then you might not like vimdiff.
On 10/13/06, Erik <mistereastenstream@gmail.com> wrote:
> I much prefer dispatch-conf. I just find it easier to use. I find
> etc-update a touch crude in the way it takes input.
>
> On 10/13/06, Remy Blank <remy.blank_asps@pobox.com> wrote:
> > maxim wexler wrote:
> > > What does the group think?
> >
> > I don't know about the group, but I use etc-update and keep all of /etc
> > in a Subversion working copy. This allows quickly seeing any changes
> > made on updates and emerges, reverting changes if anything breaks, and
> > keeping track of the reasons for specific changes in commit log messages.
> >
> > I also use a tool to store file and directory ownership and ACLs in an
> > SVN property. I believe dispatch-conf doesn't track ownership and
> > permissions.
> >
> > I even thought about using a distributed VCS like git to be able to push
> > changes to a group of machines for e.g. updates, but then again, I don't
> > have enough installations to maintain. Has anybody done something in
> > this direction?
> >
> > -- Remy
> >
> >
> > Remove underscore and suffix in reply address for a timely response.
> >
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
>
>
> --
> Erik
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-14 5:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 16:56 [gentoo-user] etc-update vs dispatch-conf maxim wexler
2006-10-13 17:49 ` Boyd Stephen Smith Jr.
2006-10-13 17:59 ` Justin Patrin
2006-10-13 18:06 ` Mark Shields
2006-10-14 5:29 ` maxim wexler
2006-10-13 18:46 ` [gentoo-user] " Remy Blank
2006-10-13 22:30 ` Erik
2006-10-14 5:21 ` Trenton Adams [this message]
2006-10-14 11:40 ` Steve Evans
2006-10-14 15:40 ` Trenton Adams
2006-10-17 21:43 ` David Grant
2006-10-14 9:46 ` [gentoo-user] " Hemmann, Volker Armin
2006-10-14 11:08 ` 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=9b1675090610132221t1a76535dl2ae9fbe7fdd58292@mail.gmail.com \
--to=trenton.d.adams@gmail.com \
--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