[Grok-dev] grok.Role

Souheil CHELFOUH trollfot at gmail.com
Mon Jan 23 14:07:59 UTC 2012


Currently, grokcore.security is part of the Cromlech stack, along with
grokcore.component and martian.
It's a good package to use, because it's small and the dependencies are limited.
zope.securitypolicy on which Role depends has those dependencies :

ZODB3
zope.annotation
zope.authentication
zope.component
zope.configuration
zope.i18nmessageid
zope.interface
zope.location
zope.schema
zope.security


zope.authentication, ZODB3 are problematic, as hard dependencies, as
some of my Cromlech project are totally ZODB free and don't involve
any kind of thing zope.authentication brings in (along with a lot of
other crappy dependencies).

So, unlesss the Role component is made optionnal with, say, an extra
"role" and  conditionnal import, I'll vote that -1, badly.


- Souheil



2012/1/23 Sylvain Viollon <sylvain at infrae.com>:
>
> Op 23 jan 2012, om 11:48 heeft Christian Klinger het volgende geschreven:
>
>> Hi,
>>
>> i don't know a reason. So i think we should move it.
>> If there are no objections i will move it.
>
>
>  I will just check how this works in Zope 2, but I don't see any blocking points
>  otherwise,
>
>  Regards,
>
>  Sylvain,
>
> --
> Sylvain Viollon -- Infrae
> t +31 10 243 7051 -- http://infrae.com
> Hoevestraat 10 3033GC Rotterdam -- The Netherlands
>
>
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev


More information about the Grok-dev mailing list