From: Ric Mesier <kilroy@WasHere.COM>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /etc/init.d
Date: 11 Mar 2002 12:54:52 -0500 [thread overview]
Message-ID: <1015869292.13991.20.camel@wubble.Genuity.COM> (raw)
In-Reply-To: <3C8CEDD8.2000907@colubris.com>
Not sure I need /etc/init.d to be touched once I have it working because
I sometimes make minor alterations to files in there that I'd rather not
get clobbered. One thing that frustrated me, tho, was the difficulty in
checking the differences in the new files in /etc. I may actually get up
the ambition to write a script to do a batch diff on all the files in
the various /etc directories.
One thing that did frustrate me while I was looking at the changes
manually was that some files showed very minor diffs. /etc/pwdb.conf
showed alterations on all the lines. Some of them, to my recollection
had the ordering changed and perhaps some spacing that was different. It
might also be useful to know why the changes were made so I can make a
determination as to whether I merge the changes in or not. Or was there
an emerge command for some of this?
Ric
On Mon, 2002-03-11 at 12:48, Yannick Koehler wrote:
>
> Guys,
>
> not sure for anyone else but is init.d really need to be protected? I
> mean does someone really change files in that directory (other than
> adding or removing)?
>
> That dir should always get merged. It would also get really nice of the
> portage could detect that no changes has been made to the file since its
> installation and therefore merge it without any issues.
>
> Like if the protected config file's time were saved in a temp files that
> portage would look into before merging to see if the date has or not
> change since the last install.
>
> Yannick Koehler
>
next prev parent reply other threads:[~2002-03-11 17:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 17:48 [gentoo-dev] /etc/init.d Yannick Koehler
2002-03-11 17:52 ` Matt Beland
2002-03-11 17:54 ` Ric Mesier [this message]
2002-03-11 18:43 ` Benjamin Ritcey
2002-03-11 18:45 ` Ric Mesier
2002-03-11 18:47 ` Ric Mesier
2002-03-11 19:55 ` Ian Smith
2002-03-11 18:02 ` Craig M. Reece
2002-03-11 18:16 ` Yannick Koehler
2002-03-11 18:52 ` mbutcher
2002-03-11 19:05 ` Craig M. Reece
2002-03-11 21:11 ` Yannick Koehler
2002-03-11 18:54 ` Matt Beland
2002-03-11 19:43 ` Martin Schlemmer
2002-03-11 20:44 ` Yannick Koehler
2002-03-11 21:10 ` Martin Schlemmer
2002-03-11 22:16 ` Matt Beland
2002-03-11 23:28 ` Yannick Koehler
2002-03-11 18:45 ` Per Wigren
2002-03-11 19:06 ` Craig M. Reece
2002-03-11 19:35 ` Yannick Koehler
2002-03-11 18:17 ` Yannick Koehler
2002-03-11 18:42 ` Matt Beland
2002-03-11 19:32 ` Yannick Koehler
2002-03-11 19:37 ` Ric Mesier
2002-03-11 21:13 ` Yannick Koehler
2002-03-11 22:07 ` Defresne Sylvain
2002-03-11 22:42 ` Ian Smith
2002-03-11 22:49 ` Defresne Sylvain
2002-03-11 22:55 ` Martin Schlemmer
2002-03-11 23:12 ` Ian Smith
2002-03-11 23:29 ` Yannick Koehler
2002-03-11 22:28 ` Ian Smith
2002-03-11 22:33 ` Ian Smith
2002-03-11 19:50 ` Martin Schlemmer
2002-03-11 19:56 ` Matt Beland
2002-03-11 21:25 ` Yannick Koehler
2002-03-11 18:41 ` Thilo Bangert
2002-03-11 19:49 ` Joachim Blaabjerg
2002-03-11 21:15 ` Yannick Koehler
2002-03-11 21:03 ` Tod M. Neidt
2002-03-11 21:30 ` Yannick Koehler
2002-03-11 16:26 ` Bob Phan
2002-03-11 21:39 ` Craig M. Reece
2002-03-11 16:42 ` Bob Phan
2002-03-11 22:33 ` [gentoo-dev] /etc/init.d the real question!? Corvus Corax
2002-03-11 23:33 ` Yannick Koehler
2002-03-12 11:03 ` [gentoo-dev] /etc/init.d Craig M. Reece
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=1015869292.13991.20.camel@wubble.Genuity.COM \
--to=kilroy@washere.com \
--cc=gentoo-dev@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