| 1 |
Neil Bothwick wrote: |
| 2 |
> On Wed, 05 Oct 2005 23:43:34 +0200, Remy Blank wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>>On the first one, both /etc/init.d/alsasound and /etc/conf.d/alsasound |
| 6 |
>>were updated, so I was asked to run etc-update, I accepted the update, |
| 7 |
>>and that was it. |
| 8 |
>> |
| 9 |
>>On the second computer, no update to these files was proposed. |
| 10 |
> |
| 11 |
> |
| 12 |
> What is the output from |
| 13 |
> |
| 14 |
> emerge --info | grep CONFIG |
| 15 |
> |
| 16 |
> on both computers? |
| 17 |
|
| 18 |
On the one that did the update: |
| 19 |
|
| 20 |
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config |
| 21 |
/usr/share/config /var/bind /var/qmail/control" |
| 22 |
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" |
| 23 |
|
| 24 |
On the one that didn't do the update: |
| 25 |
|
| 26 |
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env |
| 27 |
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config |
| 28 |
/usr/lib/X11/xkb /usr/share/config /var/qmail/control |
| 29 |
/var/www/localhost/htdocs/squirrelmail/config" |
| 30 |
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" |
| 31 |
|
| 32 |
One more fact: on the second one, I had already emerged |
| 33 |
alsa-utils-1.0.9a, and had reverted back to alsa-utils-1.0.8 with a |
| 34 |
binary package generated by quickpkg. At that time, I also reverted the |
| 35 |
config files. |
| 36 |
|
| 37 |
I played some more with it, and noticed the following: |
| 38 |
|
| 39 |
1- If I change the mtime of e.g. /etc/conf.d/alsasound to be further in |
| 40 |
the past (I set it to July), when I re-emerge alsa-utils-1.0.9a, I get |
| 41 |
the ._cfg* file and a notice that I should run etc-update. |
| 42 |
|
| 43 |
2- Then, if I reject the update, the mtime of the file doesn't change. |
| 44 |
|
| 45 |
3- If I then re-emerge alsa-utils-1.0.9a, I get *no* ._cfg* file and |
| 46 |
*no* notice to run etc-update. But I see that the file's mtime has |
| 47 |
changed to the time of the merge, even though its contents haven't |
| 48 |
changed. And in /var/db/pkg/media-sound/alsa-utils-1.0.9a/CONTENTS, the |
| 49 |
file is registered with the md5 of the *updated* file (i.e. the contents |
| 50 |
that should have ended up in the ._cfg* file). |
| 51 |
|
| 52 |
I fail to see why portage should behave differently in 1 and 3 above, if |
| 53 |
I assume that it only uses information from the filesystem. |
| 54 |
|
| 55 |
So I'm still confused about the exact rules for proposing an update to |
| 56 |
config files, and whether or not portage keeps track of *when* a user |
| 57 |
makes changes to them. |
| 58 |
|
| 59 |
-- Remy |
| 60 |
|
| 61 |
|
| 62 |
Remove underscore and suffix in reply address for a timely response. |
| 63 |
|
| 64 |
-- |
| 65 |
gentoo-user@g.o mailing list |
Archives