public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Oliver Rutherfurd" <fruhstuck@rutherfurd.net>
To: "Brian Hall" <brihall@pcisys.net>,
	"Kai Großjohann" <kai.grossjohann@uni-duisburg.de>
Cc: <gentoo-dev@gentoo.org>, <gentoo-user@gentoo.org>
Subject: Re: [gentoo-dev] Re: etc-update & ._cfg* files: major issue with gentoo?
Date: Fri, 10 Jan 2003 10:33:50 -0500	[thread overview]
Message-ID: <01d001c2b8bd$af169e20$21c0a8c0@appdevlaptop001> (raw)
In-Reply-To: 20030110152525.GA2641@pcisys.net

----- Original Message -----
> From: "Brian Hall" <brihall@pcisys.net>
> To: "Kai Großjohann" <kai.grossjohann@uni-duisburg.de>
> Cc: <gentoo-dev@gentoo.org>; <gentoo-user@gentoo.org>
> Sent: Friday, January 10, 2003 10:25 AM
> Subject: Re: [gentoo-dev] Re: etc-update & ._cfg* files: major issue with
gentoo?
>

> On Fri, Jan 10, 2003 at 12:10:57PM +0100, Kai Großjohann wrote:
> > Bengt Gorden <bengan@sunet.se> writes:
> >
> > > Kai Großjohann wrote:
> > >
> > > I maintain a RCS-repository for all the changed files in /etc. It
> > > works well for me.
> >
> > Great.  I would really appreciate something with that effect to be
> > the default, though.
>
> Seconded!

Hi,

I've written an equivalent to "etc-update" which creates backups of the
config files before replacing them. Don't know how this compares to keeping
an RCS repository, but I figured I'd mention it in case there was any
interest.

It can be found here:

http://www.rutherfurd.net/gentoo/cfghelper/

-Ollie
--
http://www.rutherfurd.net/


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-10 15:37 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 [this message]
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             ` [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='01d001c2b8bd$af169e20$21c0a8c0@appdevlaptop001' \
    --to=fruhstuck@rutherfurd.net \
    --cc=brihall@pcisys.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@gentoo.org \
    --cc=kai.grossjohann@uni-duisburg.de \
    --cc=oliver@rutherfurd.net \
    /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