On Wed, May 25, 2011 at 4:42 PM, Joan Picanyol i Puig < [email protected]> wrote:
> As stated in http://fossil-scm.org/index.html/tktview?name=ee97701f4c , > this > severely limits the usability of fossil for system configuration > management: > it's not possible to just set ignore-glob='*' and add versioned > configuration > files as needed. It's a pity, because fossil's all-in-one approach and its > statically compiled distribution make it an excellent candidate for this > use > case. > Yes, but fossil's primary purpose is a source control system, not a 100% general-purpose SCM (or maybe i'm assuming too much there), and no developer puts all his source code under the root directory (possibly another incorrect assumption). On Unix systems, the vast majority of volatile/mutable config data lives under /etc or a user's home dir, and one can of course create a fossil repo/checkout under /etc. But that brings us to another reason NOT to use fossil from your root dir for versioning arbitrary system-level config data: fossil does not support full persistence of access rights. It supports the +x bit, but Richard only added that (AFAIR) after many people bemoaned having to chmod +x their configure scripts after each checkout. Some files under, e.g., /etc require specific rights. e.g. Linux does not like it if /etc/shadow is world-readable (from what i remember, anyway) and ssh doesn't like for some files to be world-readable. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
