Dieter Maurer wrote:
> Florent Guillaume wrote at 2006-6-18 02:05 +0200:
>> ...
>> if hasattr(object,'__bobo_traverse__'):
>> subobject=object.__bobo_traverse__(request, name)
>
> If you are working on it, then you should implement a
> means that "__bobo_traverse__" can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
> Dieter Maurer wrote:
>> Florent Guillaume wrote at 2006-6-18 02:05 +0200:
>>> ...
>>> if hasattr(object,'__bobo_traverse__'):
>>> subobject=object.__bobo_traverse__(request, name)
>> If you
On 22 Jun 2006, at 14:43, Tres Seaver wrote:
Philipp von Weitershausen wrote:
Dieter Maurer wrote:
Florent Guillaume wrote at 2006-6-18 02:05 +0200:
...
if hasattr(object,'__bobo_traverse__'):
subobject=object.__bobo_traverse__(request, name)
If you are working on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I worked last night with folks from the Fedora Extras project who were
trying to package Zope 2.9.3 for FC5+. Because they were working from
the release tarball, generated by 'zpkg', much of my knowledge about how
the build process works (or doesn't)
On 6/22/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
I believe that the extra flexibility which zpkg is intended to provide
(dependency-based subset distributions, primarily) would be better
served by moving Zope to use eggs, and that we should thus retire zpkg
as the means for building Zope2 relea
Tres Seaver wrote:
> I believe that the extra flexibility which zpkg is intended to provide
> (dependency-based subset distributions, primarily) would be better
> served by moving Zope to use eggs, and that we should thus retire zpkg
> as the means for building Zope2 releases.
+1
--On 22. Juni 2006 11:01:21 -0400 Fred Drake <[EMAIL PROTECTED]> wrote:
On 6/22/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
I believe that the extra flexibility which zpkg is intended to provide
(dependency-based subset distributions, primarily) would be better
served by moving Zope to use egg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22 Jun 2006, at 16:35, Tres Seaver wrote:
I believe that the extra flexibility which zpkg is intended to provide
(dependency-based subset distributions, primarily) would be better
served by moving Zope to use eggs, and that we should thus retire
+1, back to the future...
I'll note that when I was getting this stuff done in 2.7, it was
incredibly useful to try to package Zope as an RPM (or deb, etc)
while doing itbecause you find out where all the pointy edges are.
Some of the functionality of the install routine (copyzopeskel in
Tres Seaver wrote at 2006-6-22 10:35 -0400:
> ...
>I believe that the extra flexibility which zpkg is intended to provide
>(dependency-based subset distributions, primarily) would be better
>served by moving Zope to use eggs, and that we should thus retire zpkg
>as the means for building Zope2 rele
Florent Guillaume wrote at 2006-6-22 14:50 +0200:
> ...
>> Fixing this incompatibility without breaking applications which may be
>> unknowingling dependent on it is going to be hard.
>
>Which is one of the reasons why abandoning it and moving on to Zope 3
>traversal is the only sane way to proce
Philipp von Weitershausen wrote at 2006-6-22 09:03 +0200:
>Dieter Maurer wrote:
> ...
>> If you are working on it, then you should implement a
>> means that "__bobo_traverse__" can tell the caller that
>> it should use the normal default.
> ...
>> In our private Zope version, I have used an excepti
Dieter Maurer wrote:
> Philipp von Weitershausen wrote at 2006-6-22 09:03 +0200:
>> Dieter Maurer wrote:
>> ...
>>> If you are working on it, then you should implement a
>>> means that "__bobo_traverse__" can tell the caller that
>>> it should use the normal default.
>> ...
>>> In our private Zope
13 matches
Mail list logo
