public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to work with etc-updates.
Date: Wed, 31 Aug 2005 20:16:55 -0700	[thread overview]
Message-ID: <5bdc1c8b05083120167a93c7f3@mail.gmail.com> (raw)
In-Reply-To: <43164F75.8080208@nethere.com>

On 8/31/05, Jerry Turba <jturba@nethere.com> wrote:
> Thanks everyone for your help. I will try using Marks rules and start
> using dispatch-conf to be able to roll back any changes that don't seem
> to work.
> Jerry
> 

Darn, that's scary! OK, if you're gonna follow someone as blind as me
le me expand these a bit so that I can say I really tried...

> 
> Mark Knecht wrote:

> >
> >My rules are:
> >
> >1) The update was put there for a reason.
> >
> >2) If it's a file in /etc/initd then I update it automatically.

This rule is still true. I am not a programmer and will never edit an
init script. For me these are 100% updated ASAP.

> >
> >3) If it's a file in /etc/conf.d then I update it very carefully.

This rule is true but needs some expanding on. We all edit a few
/etc/conf.d files, for hostname, rc for whether to use a tarball or
not, etc. I know the 5 or 6 that I edit. If the etc-update is for one
of those files then I generally go very carefully. Mostly I'll let
etc-update do it's thing, but I look very carefully at all changes,
and then I go back and redo my edit by hand if it's necessary when
etc-update is done.

However, today I did an emerge and etc-update wanted to do something
to /etc/conf.d/spam. Since I know I do not edit that file I just let
it do the update. No problem.

> >
> >4) If it's a file in /etc/, /etc/X11, or elsewhere the I update it
> >very carefully but possibly not right now.

This rule is still true. My experience is that xorg.conf is often more
heavily modified by me so I don't want that getting changed. I will
often make a copy of my current file and then let etc-update do it's
thing and then go back and redo my work by hand again. It's tedious,
and I know that many others would think it strange what I do,  but
seems to be the safest for me.

> >
> >5) Anything else, I go slow. Maybe I look for messages from others on
> >this list having problems before I do something.

Still true unless it looks like a file that I consider system oriented
in which case I just let it happen and hope for the best. Linux is a
tool for me. I don't do system stuff myself so if the devs want it
changed let it change.

> >
> >My experience is that rules 2 & 3 account for 80-90% of the updates.
> >

Hope this helps.

Good luck,
Mark

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-01  3:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 13:58 [gentoo-user] How to work with etc-updates Jerry Turba
2005-08-30 14:23 ` Mark Knecht
2005-09-01  0:46   ` Jerry Turba
2005-09-01  3:16     ` Mark Knecht [this message]
2005-09-01  8:09       ` Neil Bothwick
2005-10-31 17:33         ` Boyd Stephen Smith Jr.
2005-08-30 14:31 ` Roger Light
2005-08-30 14:46 ` Holly Bostick
2005-08-30 16:06   ` Eric Crossman
2005-08-30 17:15     ` Tony Davison
2005-08-30 17:22     ` Neil Bothwick
2005-08-30 21:19       ` Sean Higgins
2005-08-31  9:10         ` 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=5bdc1c8b05083120167a93c7f3@mail.gmail.com \
    --to=markknecht@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