Kent Polk wrote:
Hi shuntley (shuntley), in <862566D3.005E046B.00@ssaus1.notes.ssax.com> on Dec 7 you wrote:
I've been trying to evaluate content management systems with an eye toward whether they can be adapted to version control of code. All code version
And other types of documents as well, I hope. :^)
control packages currently extant are severly lacking to one degree or another, and it seems from my shallow knowledge that the web content providers are solving the problems the code developers are content to put up with (please observe that CVS is still the cutting edge. Gag.).
Apparently Zope supports object versioning. The Zope page mentions that the staff is about to go through the horror of setting up a public CVS tree. So allow me to ask this question:
IS IT POSSIBLE TO USE ZOPE TO STORE AND SERVE ITS OWN SOURCE?
Storing and serving is trivial.
I'll see if I can stick my foot in my mouth first. Brian or Jim can confirm if it's firmly seated there... The versioning that Zope supports is more related to a transaction model than to version *control* of documents.
Exactly, and to supporing undo (and possibly time travel). Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (540) 371-6909 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.