WebDAV locking module?
Colour me confused... I just downloaded the 2.3.2 beta tarball and tried to run our application against it. It appears that the locking module (webdav.Lockable) is missing from webdav. We develop against the CVS, and the file is there. It has been since 2.3.1 CVS - though the 2.3.1 tarball doesn't seem to have the module either... Can someone clue me in please? Richard -- Richard Jones richard@bizarsoftware.com.au Senior Software Developer, Bizar Software (www.bizarsoftware.com.au)
On Thu, Apr 19, 2001 at 09:43:02AM +1000, richard@bizarsoftware.com.au wrote:
Colour me confused...
I just downloaded the 2.3.2 beta tarball and tried to run our application against it. It appears that the locking module (webdav.Lockable) is missing from webdav. We develop against the CVS, and the file is there. It has been since 2.3.1 CVS - though the 2.3.1 tarball doesn't seem to have the module either...
No it hasn't. It is in the trunk CVS, the 2.3 branch does not have the WebDAV locks feature. Are you sure your CVS checkout is a branch checkout? -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
Martijn Pieters wrote:
On Thu, Apr 19, 2001 at 09:43:02AM +1000, richard@bizarsoftware.com.au wrote:
Colour me confused...
I just downloaded the 2.3.2 beta tarball and tried to run our application against it. It appears that the locking module (webdav.Lockable) is missing from webdav. We develop against the CVS, and the file is there. It has been since 2.3.1 CVS - though the 2.3.1 tarball doesn't seem to have the module either...
No it hasn't. It is in the trunk CVS, the 2.3 branch does not have the WebDAV locks feature. Are you sure your CVS checkout is a branch checkout?
I checkout the source using the command on the zope web site: % cvs -d :pserver:anonymous@cvs.zope.org:/cvs-repository login % cvs -z7 -d :pserver:anonymous@cvs.zope.org:/cvs-repository checkout Zope2 What's this branch you speak of? Richard -- Richard Jones richard@bizarsoftware.com.au Senior Software Developer, Bizar Software (www.bizarsoftware.com.au)
On Fri, Apr 20, 2001 at 08:49:12AM +1000, richard@bizarsoftware.com.au wrote:
I checkout the source using the command on the zope web site:
% cvs -d :pserver:anonymous@cvs.zope.org:/cvs-repository login % cvs -z7 -d :pserver:anonymous@cvs.zope.org:/cvs-repository checkout Zope2
What's this branch you speak of?
That is the trunk, the main line on the CVS server, that you are checking out. Once a Zope second-dot version goes gold, however, it gets it's own release branch, onto which we only check in bug fixes and very small features (if they are of direct benefit). So, the Zope 2.3 series has its own branch, called zope-2_3-branch. To check out from that branch, add '-d zope-2_3-branch' to your checkout command (I use the short 'co' for it): % cvs -z7 -d :pserver:anonymous@cvs.zope.org:/cvs-repository co -d zope-2_3-branch Zope2 Or you can switch an existing CVS sandbox to that tree by using the update command ('up' is the short version) in the root directory of the sandbox: % cvs -z7 up -d zope-2_3-branch Don't forget to recompile the extensions! Especially if you are using the sandbox for production systems, or development ment for production systems, you really want to avoid using the trunk! We will *very* soon be switching the trunk to requiring Python 2.1, and as you discovered, new features in the trunk will not be found in current releases. That's why we use this system.. -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
On Fri, Apr 20, 2001 at 07:43:54AM +0200, Martijn Pieters wrote:
So, the Zope 2.3 series has its own branch, called zope-2_3-branch. To check out from that branch, add '-d zope-2_3-branch' to your checkout command (I use the short 'co' for it):
% cvs -z7 -d :pserver:anonymous@cvs.zope.org:/cvs-repository co -d zope-2_3-branch Zope2
Or you can switch an existing CVS sandbox to that tree by using the update command ('up' is the short version) in the root directory of the sandbox:
% cvs -z7 up -d zope-2_3-branch
Don't forget to recompile the extensions!
Whoops, wrong switch to cvs in this email. The commands should be: % cvs -z7 -d :pserver:anonymous@cvs.zope.org:/cvs-repository co -r zope-2_3-branch Zope2 and % cvs -z7 up -r zope-2_3-branch -- Martijn Pieters | Software Engineer mailto:mj@digicool.com | Digital Creations http://www.digicool.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
participants (2)
-
Martijn Pieters -
richard＠bizarsoftware.com.au