1 |
On Mon, 2002-03-11 at 21:32, Yannick Koehler wrote: |
2 |
> Matt Beland wrote: |
3 |
> > On Mon, Mar 11, 2002 at 01:17:41PM -0500, Yannick Koehler wrote: |
4 |
> > |
5 |
> >>Yannick Koehler wrote: |
6 |
> >> |
7 |
> >>>Guys, |
8 |
> >>> |
9 |
> >>> not sure for anyone else but is init.d really need to be protected? |
10 |
> >>>I mean does someone really change files in that directory (other than |
11 |
> >>>adding or removing)? |
12 |
> >>> |
13 |
> >>> That dir should always get merged. It would also get really nice of |
14 |
> >>>the portage could detect that no changes has been made to the file since |
15 |
> >>>its installation and therefore merge it without any issues. |
16 |
> >>> |
17 |
> >>> Like if the protected config file's time were saved in a temp files |
18 |
> >>>that portage would look into before merging to see if the date has or |
19 |
> >>>not change since the last install. |
20 |
> >>> |
21 |
> >>>Yannick Koehler |
22 |
> >>> |
23 |
> >>>_______________________________________________ |
24 |
> >>>gentoo-dev mailing list |
25 |
> >>>gentoo-dev@g.o |
26 |
> >>>http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
27 |
> >>> |
28 |
> >> |
29 |
> >>Another point I have to make here is that there's a lot of files in |
30 |
> >>there and MOST people won't change them. Therefore the fact that each |
31 |
> >>time someone play in there make 80-90% people force to merge many files |
32 |
> >>is not really friendly. |
33 |
> >> |
34 |
> > |
35 |
> > Friendly, no, but it is proper behavior. Those files are critical to the |
36 |
> > proper operation of the system, and as such changes should be approached |
37 |
> > with caution. Even if you as a Gentoo user are not making any customized |
38 |
> > changes, it's a very good idea for you to be aware of changes in those |
39 |
> > files - that way, if you do emerge update --world and one of your daemons |
40 |
> > breaks, you know if there've been any changes to the init script. It may |
41 |
> > not be a critical issue for you, but it will be for some. |
42 |
> > |
43 |
> > |
44 |
> |
45 |
> While I agree they are critical, I don't agree that they are more |
46 |
> important than the program they control. And that program is emerge |
47 |
> automatically. If the script work but the program failed after an |
48 |
> emerge I think it is at the same critical level. |
49 |
> |
50 |
> Therefore I think they should be treated the same. Now they are treated |
51 |
> as config file and require end-users intervention when I don't see a |
52 |
> reason for most end-user. Like programs, some users will modify their |
53 |
> program by using personnaly modified source tree and those would know |
54 |
> not to put the binary or merge those package. |
55 |
> |
56 |
> Actually I think it's even worse treating those files as config. |
57 |
> Because new users, the one that you always want to get in a distro may |
58 |
> be running pretty old script as they may not be aware on how to do the |
59 |
> merge step manually. |
60 |
> |
61 |
|
62 |
I feel the same about this point. Especially with scripts like |
63 |
/etc/init.d/depscan.sh, /etc/init.d/runscript.sh and |
64 |
/etc/init.d/functions.sh, not updating leaded to many problems, where |
65 |
unable to boot after first time build was one of them. |
66 |
|
67 |
In the last few baselayout releases, there was major feature additions, |
68 |
rewrites, etc, making a slight diff glob, or not updating a great risk |
69 |
for creating problems. |
70 |
|
71 |
Just these should IMHO be updated realtime, and not placing a backup. |
72 |
|
73 |
> Yannick Koehler |
74 |
> |
75 |
> |
76 |
> _______________________________________________ |
77 |
> gentoo-dev mailing list |
78 |
> gentoo-dev@g.o |
79 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
80 |
-- |
81 |
|
82 |
Martin Schlemmer |
83 |
Gentoo Linux Developer, Desktop Team Developer |
84 |
Cape Town, South Africa |