Zope source code version control
Zope already supports undo via its ODB, but is it possible to do automatic versioning like CVS? That would mean no matter if I update a page (1) via Cold Fusion and then FTP up to Zope (2) via the Zope web interface I can get consistent versioning of my documents. Although I thought of somehow using CVS, it wouldn't handle both (1) and (2). If anyone can point out what's needed to make that work, I will seriously _try to_ write patches, though I don't know how difficult that would be. Is it of interest to ye developers out there? Ken Young
Ken, Since Zope is a WebDAV server, go have a look at www.webdav.org. They are starting to try and integrate cvs and webdav into just the animal you are talking about. Might be a good sart for you and they should have something soon. HTH Phil phil.harris@zope.co.uk |>-----Original Message----- |>From: zope-dev-admin@zope.org [mailto:zope-dev-admin@zope.org]On Behalf |>Of Kenneth Y.K. YOUNG |>Sent: Monday, January 10, 2000 11:36 AM |>To: Zope-Dev Mailing List |>Subject: [Zope-dev] Zope source code version control |> |> |>Zope already supports undo via its ODB, but is it possible to do automatic |>versioning like CVS? |> |>That would mean no matter if I update a page |>(1) via Cold Fusion and then FTP up to Zope |>(2) via the Zope web interface |> |>I can get consistent versioning of my documents. Although I thought of |>somehow using CVS, it wouldn't handle both (1) and (2). |> |>If anyone can point out what's needed to make that work, I will seriously |>_try to_ write patches, though I don't know how difficult that |>would be. Is |>it of interest to ye developers out there? |> |>Ken Young |> |> |>_______________________________________________ |>Zope-Dev maillist - Zope-Dev@zope.org |>http://lists.zope.org/mailman/listinfo/zope-dev |>** No cross posts or HTML encoding! ** |>(Related lists - |> http://lists.zope.org/mailman/listinfo/zope-announce |> http://lists.zope.org/mailman/listinfo/zope ) |>
"Phil Harris" <phil.harris@zope.co.uk> writes:
Might be a good sart for you and they should have something soon.
The webdav faq says: For now and for a while, CVS will still be your best bet; it is going to be a while before DAV's versioning capabilities match that of CVS. This has been the status for quite a while. What would it take to add interim CVS functionality into zope ? I mean just the most useful bare essentials - - storing & retrieving past versions - talking to standard cvs tools via the pserver protocol Enough to support, eg - cvs checkout - cvs update - cvs commit - cvs diff - cvs status Vague strategy #2.1: 1. create a ZCVSAware mixin class, which hooks into standard zope objects' get & set methods. A ZCVSAware object stores past revisions of its data and can provide a specified revision on request. This is separate from zope's undo mechanism. 2. add a pserver protocol handler to zserver Cheers and a happy new millenium to all, -Simon
[Simon Michael, on Mon, 10 Jan 2000] :: "Phil Harris" <phil.harris@zope.co.uk> writes: :: > Might be a good sart for you and they should have something soon. :: :: The webdav faq says: :: :: For now and for a while, CVS will still be your best bet; it is :: going to be a while before DAV's versioning capabilities match that :: of CVS. :: :: This has been the status for quite a while. What would it take to add :: interim CVS functionality into zope ? I mean just the most useful :: bare essentials - :: :: - storing & retrieving past versions :: - talking to standard cvs tools via the pserver protocol :: :: Enough to support, eg :: :: - cvs checkout :: - cvs update :: - cvs commit :: - cvs diff :: - cvs status This sounds wonderful. Another divergent idea, which may be bogus, but ... I'm in *love* with the whizzy new Update Agent available from RedHat Linux 6.1. This is written in Python and is open source. From either GNOME or KDE, it allows you to launch a configurable client which will automatically login in to Redhat's ftp server and download and INSTALL all security and bug fix packages that you don't already have. Literally one button push and that's it. Done. Finis. I gather from comments on the list that a high percentage of Zope users are also RedHat Linux customers. PHP is included in the standard RedHat distribution; why not Zope? If Zope were in the dist, then we RH users could keep up-to-date with Zope changes using the Update Agent. And Zope would gain the considerable marketing advantage of being on the RedHat CDROMs. Thoughts?
Zope is on the Power Tools CD from Red Hat. It is also on the Commerce Server (may be called something else) one as well. It would be nice to be on the main CD though, of course :-).
Shows I should read things properly eh! ----- Original Message ----- From: "Simon Michael" <simon@joyful.com> To: <zope-dev@zope.org> Sent: Monday, January 10, 2000 7:45 PM Subject: Re: [Zope-dev] Zope source code version control
"Phil Harris" <phil.harris@zope.co.uk> writes:
Might be a good sart for you and they should have something soon.
The webdav faq says:
For now and for a while, CVS will still be your best bet; it is going to be a while before DAV's versioning capabilities match that of CVS.
This has been the status for quite a while. What would it take to add interim CVS functionality into zope ? I mean just the most useful bare essentials -
- storing & retrieving past versions - talking to standard cvs tools via the pserver protocol
Enough to support, eg
- cvs checkout - cvs update - cvs commit - cvs diff - cvs status
Vague strategy #2.1:
1. create a ZCVSAware mixin class, which hooks into standard zope objects' get & set methods. A ZCVSAware object stores past revisions of its data and can provide a specified revision on request. This is separate from zope's undo mechanism.
2. add a pserver protocol handler to zserver
Cheers and a happy new millenium to all, -Simon
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
participants (5)
-
Hadar Pedhazur -
Kenneth Y.K. YOUNG -
Patrick Phalen -
Phil Harris -
Simon Michael