-----Original Message----- From: Jonothan Farr [mailto:jfarr@real.com] Sent: Thursday, September 23, 1999 8:35 PM To: Andrew M. Kuchling Cc: zope-dev@zope.org; zope Subject: [Zope-dev] Re: source control
What should Zope source code control look like?
Actually, after thinking about this further and discussing it with some colleagues, I've realized that what I need isn't the ability to store Zope objects in a CVS repository after all. It is the ability to use documents already stored in a CVS repository as Zope objects.
Ideally, what I need is a Zope product that implements the client side of the CVS protocol, and can allow users to check out, modify, and then commit changes to documents stored in a repository. This seems like a much easier problem to solve than storing Zope objects in CVS.
Does anyone know of an existing or planned Zope product that supports this kind of functionality?
If it can be done in Python, it can be done in Zope. The last part is usually more trivial than the first. -Michel
-jfarr
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hi! I'm a signature virus. Copy me into your .sig to join the fun! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://www.zope.org/mailman/listinfo/zope-dev
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For non-developer, user-level issues, zope@zope.org, http://www.zope.org/mailman/listinfo/zope )