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
