Chris's Wiki :: blog/sysadmin/RCSvsModernVCS Commentshttps://utcc.utoronto.ca/~cks/space/blog/sysadmin/RCSvsModernVCS?atomcommentsDWiki2009-11-23T05:55:48ZRecent comments in Chris's Wiki :: blog/sysadmin/RCSvsModernVCS.By Chris Siebenmann on /blog/sysadmin/RCSvsModernVCStag:CSpace:blog/sysadmin/RCSvsModernVCS:2c7ae2ea022f79f57c7bea0dd04ce1b32477994fChris Siebenmann<div class="wikitext"><p>For locally sensible but peculiar reasons, we are pretty much not using
anything in the Puppet/CFEngine class, and do wind up not infrequently
maintaining and versioning files in scattered directories that are not
ideal for whole-directory version control.</p>
<p>(The more I look at converting some of what we're doing over to modern
whole-directory VCSes, the more I think that you want to lay things out
in your local files area somewhat differently for such VCSes. But that's
another entry.)</p>
</div>2009-11-23T05:55:48ZFrom 98.223.162.254 on /blog/sysadmin/RCSvsModernVCStag:CSpace:blog/sysadmin/RCSvsModernVCS:b78b4a14db53c5ad8d4bc5675c1e2b559be5d3b1From 98.223.162.254<div class="wikitext"><p>An excellent point, and one I hadn't considered. The counter-argument is that is most cases, you're probably not using version control on a machine's local files. In most cases, you're probably versioning configuration files that get managed by something like CFEngine or Puppet. In that case, RCS is more a hindrance than a help. For one-off systems or files, RCS is definitely the least complicated option, but that's more of an edge case in most setups I've encountered.</p>
</div>2009-11-22T23:33:58Z