Daniel Carrera <[email protected]> writes: > Stephen J. Turnbull wrote: >> Daniel Carrera writes: >> >> > My personal opinion is that running a website directly off of a >> SCM is a > mistake. But oh well. >> >> What is a wiki (that provides history), if it's not an SCM? > > I think you know what I meant. > > In any case, I wouldn't think of a wiki as a source code management > program. A wiki might have a few things in common with an SCM, like a > history, but you don't expect a wiki to do branching and merging, > which is the central feature of an SCM (even an ancient one like CVS - > the reason you use CVS is to merge the work of developers).
If you're saying "just let everyone edit the same working tree", then you can easily lose information if two people try to edit the same wiki article at once. Moinmoin works around this, for example, with per-article advisory locking -- the same functionality seen in RCS, about the oldest and least powerful VCS around. Moinmoin also uses its own ad-hoc backend structure, which consumes TEN TIMES the disk space of the same data when stored in Darcs. Other mainstream wikis tend to use RDBMSs -- but I'm not convinced that an RDBMS is more suitable than a VCS for storing a history of changes to (mostly text) blobs. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
