From 6fc3f3012452f948d32448d2c40de60b838217a1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 11 Dec 2015 12:40:44 -0400 Subject: comment --- ...mment_1_d65fd2ebfca6b9994db9512232ce78ff._comment | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/todo/should_not_overwrite_unchanged_private_files/comment_1_d65fd2ebfca6b9994db9512232ce78ff._comment diff --git a/doc/todo/should_not_overwrite_unchanged_private_files/comment_1_d65fd2ebfca6b9994db9512232ce78ff._comment b/doc/todo/should_not_overwrite_unchanged_private_files/comment_1_d65fd2ebfca6b9994db9512232ce78ff._comment new file mode 100644 index 00000000..6e44dde6 --- /dev/null +++ b/doc/todo/should_not_overwrite_unchanged_private_files/comment_1_d65fd2ebfca6b9994db9512232ce78ff._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-12-11T16:35:43Z" + content=""" +Doesn't rebuilding propellor overwrite lots of files too? Is the +privdata.local file somehow a particular problem, perhaps becuase +of its permissions? + +You should find it easy enough to make propellor read any existing +file and only update the file when there are changes. But it seems to me +your integrity checker would still go off whenever a new version +of the file is legitimately reveiced. Perhaps it would be better to +write a property to configure your integrity checker to not fire on +this file? + +(I've thought from time to time about having rsync update the privdata.local +file. Since it's unchanged in most spins, that would probably save network +bandwidth.) +"""]] -- cgit v1.2.3