Re: [Zope3-dev] Re: ClientForm to a package
On Tue, Sep 26, 2006 at 11:08:54AM +0200, Philipp von Weitershausen wrote: Stephan Richter wrote: On Tuesday 26 September 2006 04:14, Baiju M wrote: Can we change `ClientForm` from a file based module to a package. So that others can set it as svn:external (Zope 2 ?) Let me do it in trunk? No, we are not maintaining ClientForm, so we do not have this freedom. I don't understand this. Turning it into a package would just mean moving ClientForm.py to ClientForm/__init__.py, right? Yeah, and will break the zope3 zpkg setup and Debian packages. To name just two. Just please don't back-port this. In either case, I would much prefer if we could just depend on it via eggs. +100 (But again, only on trunk.) -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: ClientForm to a package
On Tue, Sep 26, 2006 at 12:02:29PM +0200, Philipp von Weitershausen wrote: Brian Sutherland wrote: and Debian packages. I assumed they would not include ClientForm.py but simply depend on it via dpkg? Yep, thats the way it's done, but Zope 3 tarballs come with ClientForm included. To remove something from the tarball, you have to know where it is. It's also easily fixed, but probably only after a re-build, distribution and user bug reports. Not nice for a bugfix release. Just please don't back-port this. Of course not. Great, that was my only point;) In either case, I would much prefer if we could just depend on it via eggs. +100 (But again, only on trunk.) Yup. I really think buildout-ifying the Zope 3 checkout is the way to go, especially because it would also mean we could get rid of our vendor imports of 3rd party stuff and simply depend on them via setuptools. Not entirely sure what an installation package of Zope 3 will then look like, More than likely each egg would correspond to a package built from the source tarball. If you are interested, you can look at my efforts with the zc.* and hurry.* eggs/packages for the next schooltool release. The apt-source line is: deb-src ftp://ftp.schooltool.org/pub/schooltool/archives/debian unstable main You can install a python-zc.i18n package directly from there. but I assume that it will be similar to a checkout (except for development eggs): You'd download a bootstrap script that installs everything into a specified location (where everything) are eggs that are either part of the distribution or will be loaded from the zope.org. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: ClientForm to a package
Brian Sutherland wrote: On Tue, Sep 26, 2006 at 11:08:54AM +0200, Philipp von Weitershausen wrote: Stephan Richter wrote: On Tuesday 26 September 2006 04:14, Baiju M wrote: Can we change `ClientForm` from a file based module to a package. So that others can set it as svn:external (Zope 2 ?) Let me do it in trunk? No, we are not maintaining ClientForm, so we do not have this freedom. I don't understand this. Turning it into a package would just mean moving ClientForm.py to ClientForm/__init__.py, right? Yeah, and will break the zope3 zpkg setup That'd be easily fixed. and Debian packages. I assumed they would not include ClientForm.py but simply depend on it via dpkg? Just please don't back-port this. Of course not. In either case, I would much prefer if we could just depend on it via eggs. +100 (But again, only on trunk.) Yup. I really think buildout-ifying the Zope 3 checkout is the way to go, especially because it would also mean we could get rid of our vendor imports of 3rd party stuff and simply depend on them via setuptools. Not entirely sure what an installation package of Zope 3 will then look like, but I assume that it will be similar to a checkout (except for development eggs): You'd download a bootstrap script that installs everything into a specified location (where everything) are eggs that are either part of the distribution or will be loaded from the zope.org. Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: ClientForm to a package
On 9/26/06, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Brian Sutherland wrote: On Tue, Sep 26, 2006 at 11:08:54AM +0200, Philipp von Weitershausen wrote: Stephan Richter wrote: On Tuesday 26 September 2006 04:14, Baiju M wrote: Can we change `ClientForm` from a file based module to a package. So that others can set it as svn:external (Zope 2 ?) Let me do it in trunk? snip Just please don't back-port this. Of course not. Fixed in trunk (r70384) I hope this will solve this issue (development time): http://mail.zope.org/pipermail/zope3-dev/2006-August/020001.html http://mail.zope.org/pipermail/zope3-dev/2006-August/020006.html Please update Zope 2 svn:external. Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: ClientForm to a package
Stephan Richter wrote: On Tuesday 26 September 2006 04:14, Baiju M wrote: Can we change `ClientForm` from a file based module to a package. So that others can set it as svn:external (Zope 2 ?) Let me do it in trunk? No, we are not maintaining ClientForm, so we do not have this freedom. I don't understand this. Turning it into a package would just mean moving ClientForm.py to ClientForm/__init__.py, right? In either case, I would much prefer if we could just depend on it via eggs. Since Zope 2 ships with Zope 3, the module should be available. Yeah, but how do you think it ships with Zope 3? It uses svn:externals to zope and zope.app... Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
