From: daid kahl <daidxor@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How should I clean up my broken system?
Date: Mon, 22 Feb 2010 20:29:29 +0900 [thread overview]
Message-ID: <3ac129341002220329s37ee383akec3c559a9de7b0e6@mail.gmail.com> (raw)
In-Reply-To: <1266721977.3445.146.camel@localhost>
>> > > > On a more serious note, conf-update automatically merges trivial
>> > > > changes, so any configs you ran at the default, which is probably the
>> > > > majority, won't be flaged at all.
>> > >
>> > > so does cfg-update....
>> >
>> > Every now and then, someone mentions cfg-update - usually you :) - and I
>> > give it another try, but I don't really get on with it and always go back
>> > to conf-update. There's nothing specific wrong with it, I just prefer (or
>> > am used to) conf-update.
>> >
>> > I expect that if I were still using etc-update or dispatch-conf I would
>> > welcome it with open arms though.
Yay, thanks for the ideas. dispatch-conf was a welcome change from
etc-update, so this must be the next step. And just in time too, I
updated to ~x86 last week, and I left around the 11 config files that
need more than just hand waving to deal with (looks like important
changes, but I did modifications as well to those cases).
>>
>> You make me feel out of touch with Gentoo! Is dispatch-conf and etc-update
>> that bad then?
>
> out of touch would be rolling your own config update tool, like me ;)
> It hasn't changed much since I started using Gentoo...
>
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
Sharing is caring! Can we try it? More importantly, would we want to?
I'm wondering if some of these config manglers have configs
themselves, or some place to keep track of the configs I want like red
flagged to not get accidentially overwritten (sorry I didn't read the
man pages yet because I didn't get too screwed without), because I
want to keep track of the ones I edit other than some text file or my
memory "oh yeah, vim I hated the auto-line wrapping...where's that
backup from last week?"
~daid
next prev parent reply other threads:[~2010-02-22 12:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 19:55 [gentoo-user] How should I clean up my broken system? Alan Mackenzie
2010-02-12 19:55 ` Volker Armin Hemmann
2010-02-12 21:21 ` Kyle Bader
2010-02-12 22:52 ` Neil Bothwick
2010-02-13 7:28 ` Alan McKinnon
2010-02-13 20:43 ` Neil Bothwick
2010-02-14 6:01 ` Alan McKinnon
2010-02-14 9:34 ` Neil Bothwick
2010-02-14 11:03 ` Volker Armin Hemmann
2010-02-14 11:32 ` Neil Bothwick
2010-02-20 12:08 ` Mick
2010-02-20 12:20 ` Volker Armin Hemmann
2010-02-21 0:22 ` Neil Bothwick
2010-02-21 3:12 ` Iain Buchanan
2010-02-22 11:29 ` daid kahl [this message]
2010-02-22 13:56 ` Volker Armin Hemmann
2010-02-22 17:06 ` [gentoo-user] " Harry Putnam
2010-02-26 7:29 ` daid kahl
2010-02-26 18:20 ` [gentoo-user] " Peter Humphrey
2010-02-26 18:47 ` Alex Schuster
2010-02-27 1:02 ` Peter Humphrey
2010-02-12 23:46 ` William Kenworthy
2010-02-13 7:27 ` Alan McKinnon
2010-02-13 17:51 ` Alan Mackenzie
2010-02-13 18:50 ` Stroller
2010-02-14 6:00 ` Alan McKinnon
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=3ac129341002220329s37ee383akec3c559a9de7b0e6@mail.gmail.com \
--to=daidxor@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