On 2006-12-28 21:03:57 +0100, Paul Slootman wrote: > This is I think a question of interpretation; > if the local change modifies the way the package works in any way, then > I agree; but a comment?! Where does it end? Do you want upgrades to > preserve the mtime of the configuration file as well? How about the > filesize, if that was changed locally?
A comment can contain valuable information. For instance, the admin could add a note about why he set some value. IMHO, comments should be preserved, and at least, should be assumed to be preserved unless said otherwise. Preserving the mtime doesn't make any sense (unless the file has not changed, in which case it may be a good idea to preserve it, but anyway, this is not a user information). The filesize is implied by the file contents, and isn't a user information either. If really you can't preserve the comments, it must be said at the beginning of the configuration file. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
