1 |
One way these conflicts could be reduced is by separating out sections in |
2 |
config files that will most probably be modified by the user and those which |
3 |
are not. For example the USE directive and the CFLAGS directive from |
4 |
make.conf could be moved to a separate file. That way whenever portage |
5 |
changes, they wouldnt need to update those flags (or even if they did it |
6 |
would be easy to merge). This is in ofcourse be in addition to having a way |
7 |
for the user to indicate which files he is interested in and hence those |
8 |
files should not be auto updated. Also maintaining a history of updates in a |
9 |
separate directory would also |
10 |
help. This way in case things do go wrong we still have access to the old |
11 |
files. |
12 |
|
13 |
Balaji |
14 |
|
15 |
-----Original Message----- |
16 |
From: Jason Giangrande [mailto:jason@××××××××××.org] |
17 |
Sent: Thursday, March 06, 2003 11:30 AM |
18 |
To: gentoo-user@g.o |
19 |
Subject: Re: [gentoo-user] etc-update |
20 |
|
21 |
|
22 |
Ian, that was my point exactly. |
23 |
|
24 |
I'm not saying that, by default, etc-update should update all files |
25 |
automatically but being able to tell it to update all files that I know |
26 |
I haven't manually changed would be a good thing. |
27 |
|
28 |
Jason |
29 |
|
30 |
Ian Truelsen wrote: |
31 |
|
32 |
>On Thu, 6 Mar 2003 13:53:00 -0500 |
33 |
>"Todd Punderson" <todd@××××××.net> wrote: |
34 |
> |
35 |
> |
36 |
> |
37 |
>>Blindly merging new config files is extremely dangerous. As much of a |
38 |
>>pain as it is, it is of utmost importance that you take the time to |
39 |
>>review the changes and be sure they make sense for your system. You |
40 |
>>surely wouldn't want your make.conf to just be overwritten. Not |
41 |
>>updating or blindly updating the files in /etc is probably one of the |
42 |
>>top reasons for system problems. There is a nice new feature that will |
43 |
>>automatically update insignificant changes to the config files. Check |
44 |
>>out /etc/etc-update.conf. Todd |
45 |
>> |
46 |
>> |
47 |
>> |
48 |
>True enough, but isn't there some way that we could track whether a |
49 |
>config file has been altered? It seems to me that, except in very odd |
50 |
>cases, a config file that has not been altered could just be updated |
51 |
>automatically. |
52 |
> |
53 |
>Of course, I may be biased by having just updated to X 4.3 and had to |
54 |
>cruise through 75 config files in etc-update. I think I wore out the |
55 |
>colon and q keys :) |
56 |
> |
57 |
> |
58 |
> |
59 |
|
60 |
-- |
61 |
-Jason Giangrande |
62 |
giangrande.org - http://www.giangrande.org <http://www.giangrande.org/> |
63 |
Dog's I View - http://www.dogsiview.com <http://www.dogsiview.com/> |
64 |
|
65 |
|
66 |
-- |
67 |
gentoo-user@g.o mailing list |
68 |
|
69 |
-- |
70 |
gentoo-dev@g.o mailing list |