Hey all, I'm working on a revised build process for Zope 2.9, based on the work that we've done for Zope 3. What this means is that we'll have a setup.py that uses the code from zpkg (http://www.zope.org/Members/fdrake/zpkgtools/) to load metadata from the various packages are part of the checkout, and use distutils to perform the build. One thing that will need to change is the makefile that gets generated by the configure script. The current makefile has an enormous number of options that don't really seem to make sense, and many targets. I'd like to remove any that aren't being actively used, but it's hard to tell which those are. Would anyone object if we switch to something a lot closer to the Zope 3 makefile? There's basically in-place builds and tests, and that's it. Everything else is handled outside the makefile. Comments or objections? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> Zope Corporation
If there are no sane <wink> objections, I'd like to move Zope trunk to using ZODB 3.5 tomorrow (Friday). Zope3 has been using ZODB 3.5 for months, and the intent has been that the ZODB 3.4 line survive for the sake of the Zope 2.8 line (as the ZODB 3.2 line survives for the sake of the Zope 2.7 line). Having Zope 2.9 and Zope3 use the same ZODB version should make sharing of Zope code across versions easier, allow 2.9 to exploit new ZODB features, and enable both Zopes to use the same, new zpkg-based build mechanisms. A related changed would happen soon after (probably also on Friday): the ExtensionClass-based Persistence package still lives in the ZODB part of the repository, despite that it can't even be compiled from a ZODB checkout (the prerequisite ExtensionClass implementation lives in the Zope part of the repository). So the plan there is to remove the svn:externals stitching Persistence into Zope from ZODB, and move the Persistence package from ZODB trunk to Zope trunk. In all, this one is just minor fiddling, but sane objections to this are welcome too.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tim Peters wrote:
If there are no sane <wink> objections, I'd like to move Zope trunk to using ZODB 3.5 tomorrow (Friday). Zope3 has been using ZODB 3.5 for months, and the intent has been that the ZODB 3.4 line survive for the sake of the Zope 2.8 line (as the ZODB 3.2 line survives for the sake of the Zope 2.7 line). Having Zope 2.9 and Zope3 use the same ZODB version should make sharing of Zope code across versions easier, allow 2.9 to exploit new ZODB features, and enable both Zopes to use the same, new zpkg-based build mechanisms.
+1.
A related changed would happen soon after (probably also on Friday): the ExtensionClass-based Persistence package still lives in the ZODB part of the repository, despite that it can't even be compiled from a ZODB checkout (the prerequisite ExtensionClass implementation lives in the Zope part of the repository). So the plan there is to remove the svn:externals stitching Persistence into Zope from ZODB, and move the Persistence package from ZODB trunk to Zope trunk. In all, this one is just minor fiddling, but sane objections to this are welcome too.
+1 for that, too. Maybe-insane-but-not-crazy-enough-to-argue-with-timbot'ly, Tres - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDDix6+gerLs4ltQ4RAlRoAJ4yPJBc18c2qC1Ha52jV855u/6AggCgupqB wNihskKC52Ur1dKnqJSQBaM= =+1Xo -----END PGP SIGNATURE-----
Heads up! If you have a Zope trunk checkout, you'll need to recursively delete directory lib/python/Persistence before an update will succeed. If you try to update before deleting that directory, you'll see something like: Failed to add directory 'lib/python/Persistence': object of the same name already exists. You may also need to do "svn cleanup" and try again, if you don't delete the directory before trying to update. [Tim Peters]
If there are no sane <wink> objections, I'd like to move Zope trunk to using ZODB 3.5 tomorrow (Friday). ...
This didn't happen. There's a chicken-and-egg problem with incorporating zpkg changes too, and that's probably going to wait for a newer release of Five.
A related changed would happen soon after (probably also on Friday): the ExtensionClass-based Persistence package still lives in the ZODB part of the repository, despite that it can't even be compiled from a ZODB checkout (the prerequisite ExtensionClass implementation lives in the Zope part of the repository). So the plan there is to remove the svn:externals stitching Persistence into Zope from ZODB, and move the Persistence package from ZODB trunk to Zope trunk.
That part did happen. Removing the svn:externals line for Persistence from Zope trunk's lib/python, followed by an ``svn move`` of the Persistence package (from ZODB trunk to Zope trunk), caused the headaches at the top of this message. I'm afraid current SVN gets a bit lost when switching from copies to externals, or vice versa.
participants (3)
-
Fred Drake -
Tim Peters -
Tres Seaver