| 1 |
Marius Mauch wrote: |
| 2 |
|
| 3 |
> On 05/02/04 Stuart Herbert wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>On Sunday 02 May 2004 15:27, Marius Mauch wrote: |
| 7 |
>> |
| 8 |
>>>http://article.gmane.org/gmane.linux.gentoo.devel/16090 |
| 9 |
>> |
| 10 |
>>Hmmm ... according to that, you're still planning to have the ._cfg |
| 11 |
>>files? |
| 12 |
> |
| 13 |
> |
| 14 |
> Yes, but they will just be diffs of the changes between the old and new |
| 15 |
> original config files, so for example you won't get asked to update |
| 16 |
> /etc/fstab for each baselayout update, and if there are changes you |
| 17 |
> don't risk to nuke your modified version completely. |
| 18 |
> |
| 19 |
> Marius |
| 20 |
> |
| 21 |
|
| 22 |
dispatch-conf already does this doesn't it? and.. that idea is broken |
| 23 |
anyway.. consider |
| 24 |
|
| 25 |
user installs app X, makes extensive changes to config files |
| 26 |
|
| 27 |
user upgrades app X, app X still uses config files (ie: syntax hasn't |
| 28 |
changed) |
| 29 |
|
| 30 |
do the last step many many times (routine upgrades), in which case |
| 31 |
etc-update doesn't ask you to change the files since they didn't change |
| 32 |
since last time |
| 33 |
|
| 34 |
user upgrades app X again, which has a totally new config syntax and |
| 35 |
etc-config unknowingly gets rid of the ._cfg files seeing that nothing |
| 36 |
has changed from last time.. |
| 37 |
|
| 38 |
dispatch-conf is really the direction we should go though, since it |
| 39 |
would allow you to merge between arbitrary versions, ie (this started |
| 40 |
acting funny last week after i upgraded, I better diff the current |
| 41 |
config and the one from that upgrade to see if there are any changes i |
| 42 |
need to merge) |
| 43 |
|
| 44 |
perhaps they should be combined to make the dispatch-conf behaviour an |
| 45 |
option of etc-update. |
| 46 |
|
| 47 |
Joshua Brindle |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives