Christof Lange wrote:
>
> I am afraid that I have to continue re-grading file by file
> (and in mime.cfg even line by line) with every new distribution...
>
> Christof Lange
>
> PS: Just another idea: what about using the read-only attribute to
> mark those files you do not want to be overwritten?
Hi Christof;
Thanks for your kind words.
Well, clearing ALL the archive bits when you load a new version should still
help reduce the work both immediately and way down the line. Although, I must
admit, when it is severely customized it's depressing to even think about
it unless you are as organized as Glenn McCorkle. <g>
As far as the read-only bits go, that might work if you want to overlay the
new on top of the old, but it's still a lot of work and lacks the automatic
flagging feature for further changes. Also, you can't leave some files (like
Arachne.,cfg) as read-only. She re-writes it a lot more than you might think.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
