| 1 |
Matt Beland wrote: |
| 2 |
> On Mon, Mar 11, 2002 at 01:17:41PM -0500, Yannick Koehler wrote: |
| 3 |
> |
| 4 |
>>Yannick Koehler wrote: |
| 5 |
>> |
| 6 |
>>>Guys, |
| 7 |
>>> |
| 8 |
>>> not sure for anyone else but is init.d really need to be protected? |
| 9 |
>>>I mean does someone really change files in that directory (other than |
| 10 |
>>>adding or removing)? |
| 11 |
>>> |
| 12 |
>>> That dir should always get merged. It would also get really nice of |
| 13 |
>>>the portage could detect that no changes has been made to the file since |
| 14 |
>>>its installation and therefore merge it without any issues. |
| 15 |
>>> |
| 16 |
>>> Like if the protected config file's time were saved in a temp files |
| 17 |
>>>that portage would look into before merging to see if the date has or |
| 18 |
>>>not change since the last install. |
| 19 |
>>> |
| 20 |
>>>Yannick Koehler |
| 21 |
>>> |
| 22 |
>>>_______________________________________________ |
| 23 |
>>>gentoo-dev mailing list |
| 24 |
>>>gentoo-dev@g.o |
| 25 |
>>>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 26 |
>>> |
| 27 |
>> |
| 28 |
>>Another point I have to make here is that there's a lot of files in |
| 29 |
>>there and MOST people won't change them. Therefore the fact that each |
| 30 |
>>time someone play in there make 80-90% people force to merge many files |
| 31 |
>>is not really friendly. |
| 32 |
>> |
| 33 |
> |
| 34 |
> Friendly, no, but it is proper behavior. Those files are critical to the |
| 35 |
> proper operation of the system, and as such changes should be approached |
| 36 |
> with caution. Even if you as a Gentoo user are not making any customized |
| 37 |
> changes, it's a very good idea for you to be aware of changes in those |
| 38 |
> files - that way, if you do emerge update --world and one of your daemons |
| 39 |
> breaks, you know if there've been any changes to the init script. It may |
| 40 |
> not be a critical issue for you, but it will be for some. |
| 41 |
> |
| 42 |
> |
| 43 |
|
| 44 |
While I agree they are critical, I don't agree that they are more |
| 45 |
important than the program they control. And that program is emerge |
| 46 |
automatically. If the script work but the program failed after an |
| 47 |
emerge I think it is at the same critical level. |
| 48 |
|
| 49 |
Therefore I think they should be treated the same. Now they are treated |
| 50 |
as config file and require end-users intervention when I don't see a |
| 51 |
reason for most end-user. Like programs, some users will modify their |
| 52 |
program by using personnaly modified source tree and those would know |
| 53 |
not to put the binary or merge those package. |
| 54 |
|
| 55 |
Actually I think it's even worse treating those files as config. |
| 56 |
Because new users, the one that you always want to get in a distro may |
| 57 |
be running pretty old script as they may not be aware on how to do the |
| 58 |
merge step manually. |
| 59 |
|
| 60 |
Yannick Koehler |
Archives