[Community] zgeo.geographer - Zope 2.12 and Plone4
sean.gillies at gmail.com
Fri Jun 25 14:02:46 EEST 2010
On Thu, Jun 24, 2010 at 12:21 PM, Giorgio Borelli
<giorgio at giorgioborelli.it> wrote:
> Hi Sean,
> Il giorno 23/giu/2010, alle ore 12.00, Sean Gillies ha scritto:
>> On Thu, Jun 17, 2010 at 2:19 PM, Giorgio Borelli
>> <giorgio at giorgioborelli.it> wrote:
>>> Hi Sean,
>>> Il giorno 21/mag/2010, alle ore 14.16, Sean Gillies ha scritto:
>>>> I'm not sure how this got truncated.
>>>> Could we detect the presence of zope.security or zope.app.security and
>>>> include the appropriate one for 2.10 or 2.12?
>>> I tried differents approachs to fix this but I haven't find another solution.
>>> I tried to add differents zcml:condition which don't resolve the problem (zope.security and zope.app.security are present in both Zope versions) and I have tried to unconfigure the zcml declaration which raises the error .
>>> The bug which affects zgeo.geographer/collective.geo.geographer is documented ad this url - https://bugs.launchpad.net/zope3/+bug/507563 - and its state is 'won't Fix' because the zope.localpermission package is deprecated.
>>> (I don't understand why although it's deprecated, zope.security depends on it :( )
>>>> We're doing this for
>>>> another package at least one other place in the zgeo namespace
>>> Do you remember where you are doing this? I searched in the gispython trac but I haven't find anything about it.
>> I apologize for being so late with this reply :( I searched too and it
>> looks like I'm no longer using zcml:condition like this
> "Plone4, or not Plone4: that is the question" :-)
> I think zcml:contidion works fine when you can discern the presence of an installed package. In this case we can't do it.
> I haven't yet choosed the best way to fix that problem. I think there are two way to do that but both choices break the compatibility with previous Zope versions.
> We can modify zgeo.geographer to include the patch but, if you aren't interested in doing that, I can include the functionalities defined in zgeo.geographer in c.geo.geographer package.
> what do you think about that?
The only reason I've included zope.app.security in zgeo.geographer's
ZCML is to define permissions for the georeferencing annotator
No zope security package is imported anywhere in zgeo.geographer.
Maybe there's a more compatible way to define the permissions and then
we could drop inclusion of zope.security or zope.app.security in the
More information about the Community