From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1ENHBH-0001Xh-NI for garchives@archives.gentoo.org; Wed, 05 Oct 2005 21:52:08 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j95Lg0RY007895; Wed, 5 Oct 2005 21:42:00 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j95Lac7e001395 for ; Wed, 5 Oct 2005 21:36:38 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.43) id 1ENH4W-0005KH-CC for gentoo-user@lists.gentoo.org; Wed, 05 Oct 2005 21:45:08 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1ENH4N-0003xV-GE for gentoo-user@gentoo.org; Wed, 05 Oct 2005 23:44:59 +0200 Received: from dhcp-83-219-107-159.customers.tvtnet.ch ([83.219.107.159]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Oct 2005 23:44:59 +0200 Received: from remy.blank_asps by dhcp-83-219-107-159.customers.tvtnet.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Oct 2005 23:44:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Remy Blank Subject: [gentoo-user] Merging of config files in /etc Date: Wed, 05 Oct 2005 23:43:34 +0200 Message-ID: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dhcp-83-219-107-159.customers.tvtnet.ch User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050817) X-Accept-Language: en-us, en Sender: news X-Archives-Salt: ef4cf694-1657-4457-ac2c-15c45ed75fc5 X-Archives-Hash: d54896c404dd97aa343e99dfdadfe95b I thought I knew how configuration files in /etc were updated by portage until I updated alsa-utils this evening on two computers. Both had 1.0.8 installed, and I updated both to 1.0.9a with: emerge -uDpv alsa-utils 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. While merging, portage just seemed to assume they were already fine: --- /etc/ --- /etc/conf.d/ >>> /etc/conf.d/alsasound --- /etc/modules.d/ >>> /etc/modules.d/alsa --- /etc/init.d/ >>> /etc/init.d/alsasound The strange thing is, both files started identical on both computers. This means that I had lost an update on the second computer, as both files still had the old content. Now, I had already noticed that when a package was updated that made changes to files in /etc, and the changes were merged with etc-update, and then the same package was re-emerged, then no updates to the file were done anymore. I had assumed that portage somehow kept track of etc-update runs. But the situation above doesn't seem to fall in this category, as there was definitely an update to the files. So my questions: - What are the rules that portage uses to decide if an update to configuration files in /etc should be proposed to the user (by merging the file as ._cfg0000_*) or just dropped? - How do I make sure that I don't miss an update to configuration files, like was the case above? Thank you. -- Remy Remove underscore and suffix in reply address for a timely response. -- gentoo-user@gentoo.org mailing list