| 1 |
Not sure I need /etc/init.d to be touched once I have it working because |
| 2 |
I sometimes make minor alterations to files in there that I'd rather not |
| 3 |
get clobbered. One thing that frustrated me, tho, was the difficulty in |
| 4 |
checking the differences in the new files in /etc. I may actually get up |
| 5 |
the ambition to write a script to do a batch diff on all the files in |
| 6 |
the various /etc directories. |
| 7 |
|
| 8 |
One thing that did frustrate me while I was looking at the changes |
| 9 |
manually was that some files showed very minor diffs. /etc/pwdb.conf |
| 10 |
showed alterations on all the lines. Some of them, to my recollection |
| 11 |
had the ordering changed and perhaps some spacing that was different. It |
| 12 |
might also be useful to know why the changes were made so I can make a |
| 13 |
determination as to whether I merge the changes in or not. Or was there |
| 14 |
an emerge command for some of this? |
| 15 |
|
| 16 |
Ric |
| 17 |
|
| 18 |
|
| 19 |
On Mon, 2002-03-11 at 12:48, Yannick Koehler wrote: |
| 20 |
> |
| 21 |
> Guys, |
| 22 |
> |
| 23 |
> not sure for anyone else but is init.d really need to be protected? I |
| 24 |
> mean does someone really change files in that directory (other than |
| 25 |
> adding or removing)? |
| 26 |
> |
| 27 |
> That dir should always get merged. It would also get really nice of the |
| 28 |
> portage could detect that no changes has been made to the file since its |
| 29 |
> installation and therefore merge it without any issues. |
| 30 |
> |
| 31 |
> Like if the protected config file's time were saved in a temp files that |
| 32 |
> portage would look into before merging to see if the date has or not |
| 33 |
> change since the last install. |
| 34 |
> |
| 35 |
> Yannick Koehler |
| 36 |
> |
Archives