public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Remy Blank <remy.blank_asps@pobox.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: Merging of config files in /etc
Date: Thu, 06 Oct 2005 09:51:27 +0200	[thread overview]
Message-ID: <di2l20$f1n$1@sea.gmane.org> (raw)
In-Reply-To: <20051005232914.2041f150@hactar.digimed.co.uk>

Neil Bothwick wrote:
> On Wed, 05 Oct 2005 23:43:34 +0200, Remy Blank wrote:
> 
> 
>>On the first one, both /etc/init.d/alsasound and /etc/conf.d/alsasound
>>were updated, so I was asked to run etc-update, I accepted the update,
>>and that was it.
>>
>>On the second computer, no update to these files was proposed.
> 
> 
> What is the output from
> 
> emerge --info | grep CONFIG
> 
> on both computers?

On the one that did the update:

CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"

On the one that didn't do the update:

CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control
/var/www/localhost/htdocs/squirrelmail/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"

One more fact: on the second one, I had already emerged
alsa-utils-1.0.9a, and had reverted back to alsa-utils-1.0.8 with a
binary package generated by quickpkg. At that time, I also reverted the
config files.

I played some more with it, and noticed the following:

 1- If I change the mtime of e.g. /etc/conf.d/alsasound to be further in
the past (I set it to July), when I re-emerge alsa-utils-1.0.9a, I get
the ._cfg* file and a notice that I should run etc-update.

 2- Then, if I reject the update, the mtime of the file doesn't change.

 3- If I then re-emerge alsa-utils-1.0.9a, I get *no* ._cfg* file and
*no* notice to run etc-update. But I see that the file's mtime has
changed to the time of the merge, even though its contents haven't
changed. And in /var/db/pkg/media-sound/alsa-utils-1.0.9a/CONTENTS, the
file is registered with the md5 of the *updated* file (i.e. the contents
that should have ended up in the ._cfg* file).

I fail to see why portage should behave differently in 1 and 3 above, if
I assume that it only uses information from the filesystem.

So I'm still confused about the exact rules for proposing an update to
config files, and whether or not portage keeps track of *when* a user
makes changes to them.

-- Remy


Remove underscore and suffix in reply address for a timely response.

-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2005-10-06  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 21:43 [gentoo-user] Merging of config files in /etc Remy Blank
2005-10-05 22:29 ` Neil Bothwick
2005-10-06  7:51   ` Remy Blank [this message]

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='di2l20$f1n$1@sea.gmane.org' \
    --to=remy.blank_asps@pobox.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