| 1 |
Per Wigren wrote: |
| 2 |
> How about having a "magic line" like: |
| 3 |
> ###PROTECTED### |
| 4 |
> or something? Then emerge can overwrite the file if that line doesn't exist.. |
| 5 |
> |
| 6 |
> // Wigren |
| 7 |
> |
| 8 |
|
| 9 |
I think it would be better to have a file outside the one which need to |
| 10 |
be protected that know/record which one has to be. Let's say it's a |
| 11 |
config file and the end-user got a config-file from the web, if he just |
| 12 |
copy the file over the old one he will get f... the next emerge. The |
| 13 |
current system is ok, the directory to protect are saved outside the |
| 14 |
config directory and you need to know where they are to mess with them. |
| 15 |
They actually could get more flexible and have regexp/more granular |
| 16 |
selection in them thought. |
| 17 |
|
| 18 |
Yannick Koehler |
Archives