| 1 |
On Mon, Mar 11, 2002 at 01:17:41PM -0500, Yannick Koehler wrote: |
| 2 |
> Yannick Koehler wrote: |
| 3 |
> > |
| 4 |
> >Guys, |
| 5 |
> > |
| 6 |
> > not sure for anyone else but is init.d really need to be protected? |
| 7 |
> >I mean does someone really change files in that directory (other than |
| 8 |
> >adding or removing)? |
| 9 |
> > |
| 10 |
> > That dir should always get merged. It would also get really nice of |
| 11 |
> >the portage could detect that no changes has been made to the file since |
| 12 |
> >its installation and therefore merge it without any issues. |
| 13 |
> > |
| 14 |
> > Like if the protected config file's time were saved in a temp files |
| 15 |
> >that portage would look into before merging to see if the date has or |
| 16 |
> >not change since the last install. |
| 17 |
> > |
| 18 |
> >Yannick Koehler |
| 19 |
> > |
| 20 |
> >_______________________________________________ |
| 21 |
> >gentoo-dev mailing list |
| 22 |
> >gentoo-dev@g.o |
| 23 |
> >http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 24 |
> |
| 25 |
> |
| 26 |
> Another point I have to make here is that there's a lot of files in |
| 27 |
> there and MOST people won't change them. Therefore the fact that each |
| 28 |
> time someone play in there make 80-90% people force to merge many files |
| 29 |
> is not really friendly. |
| 30 |
|
| 31 |
Friendly, no, but it is proper behavior. Those files are critical to the |
| 32 |
proper operation of the system, and as such changes should be approached |
| 33 |
with caution. Even if you as a Gentoo user are not making any customized |
| 34 |
changes, it's a very good idea for you to be aware of changes in those |
| 35 |
files - that way, if you do emerge update --world and one of your daemons |
| 36 |
breaks, you know if there've been any changes to the init script. It may |
| 37 |
not be a critical issue for you, but it will be for some. |
| 38 |
|
| 39 |
-- |
| 40 |
Matt Beland |
| 41 |
matt@××××××××××××××.org |
| 42 |
http://www.rearviewmirror.org |
Archives