> From this (thanks to lintian now I have the proper link :) ) > > https://lintian.debian.org/tags/control-file-has-bad-permissions.html > https://www.debian.org/doc/debian-policy/ch-files.html#s-permissions-owners > > all control files: > - should be owned by root:root (+ I would say uid/gid 0/0, because root may > be mapped) which is the case now > - should be 755 or 644, depending if they are executable or not > > The number of files that should be 755 are limited to (according to > linitian) config, postinst, postrm, preinst, and prerm. All others should be > 644. > > So I would say without loss of generality, we can set the permission to 644 > except for those config, postinst... files . I can send you a patch based on > 76c59007dd3944e23848b7d5912a59a7d3db6398 today (and update the doc > accordingly). > > Is that good for you?
Sounds good. Those rules are written as guidelines and I'm not certain how often they are broken so could you also add a single variable for toggling between defaults described above and using file permissions as provided? Thanks, Domen -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
