| 1 |
On Tue, 2 Jan 2007, Alan McKinnon wrote: |
| 2 |
|
| 3 |
> On Tuesday 02 January 2007 08:50, Daniel Barkalow wrote: |
| 4 |
> > I also think that emerge should keep track of the config files |
| 5 |
> > installed by packages, so that etc-update knows if you've got local |
| 6 |
> > modifications, and give you a big warning when you might lose a |
| 7 |
> > change you made. |
| 8 |
> |
| 9 |
> Huh? Portage already does this. Standard config dirs are |
| 10 |
> CONFIG_PROTECTed which is where etc-update comes in. It will merge |
| 11 |
> trivial changes (whitespace, etc) and let *you* chose what to do for |
| 12 |
> everything else. You get to keep the original file, use the update, or |
| 13 |
> use a customized merge of the two. |
| 14 |
|
| 15 |
The issue is that etc-update doesn't have the version of the config file |
| 16 |
as installed by the version of the package that's being replaced, so it |
| 17 |
can't tell the difference between non-trivial changes to the config file |
| 18 |
as shipped by gentoo between the old version and the new version and |
| 19 |
non-trivial local modifications that I've made myself to a config file |
| 20 |
which has not been changed between package versions. I've definitely had |
| 21 |
etc-update ask for confirmation on files I'm sure I didn't change |
| 22 |
(including, in some cases, executables that get installed in protected |
| 23 |
directories). |
| 24 |
|
| 25 |
> There is no need to give you a big warning if you might lose a change - |
| 26 |
> the very act of running etc-update at all IS that warning. It's |
| 27 |
> understood that if the new file shows up, then you DO have local |
| 28 |
> modifications |
| 29 |
|
| 30 |
It's understood that there is a difference between what I'm using now and |
| 31 |
what new package comes with. But there's no information on whether that |
| 32 |
difference came from local modifications. |
| 33 |
|
| 34 |
-Daniel |
| 35 |
*This .sig left intentionally blank* |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives