-----BEGIN PGP SIGNED MESSAGE-----
Jim Fulton wrote:
> On Fri, Apr 23, 2010 at 4:18 AM, Jacob Holm <j...@improva.dk> wrote:
>> Hi Michael, Tres
>> I agree a new major version is required due to the new "feature" of
>> having new permission names, but there is no reason to break
>> compatibility with code using the old names.
>> IIRC the <redefinePermission/> zcml-directive is there exactly to
>> provide backwards compatibility when renaming permissions. Use like:
>> from = "<no longer defined permisison id>"
>> to = "<existing permission id>"
>> It is defined in zope.security:meta.zcml along with the <permission/>
>> directive, so should be usable with any code that uses that.
> This only affects ZCML. It caused declarations for the old permission
> to be mapped to the new one. It doesn't affect stored permissions.
Maybe the short-term fix would be to add a shim package (reviving
'zope.app.dublincore', maybe) whose only job in life is to make those
permissions loadable. Maybe the package ships with some code to help
write the evolve script, or something.
In the meanwhile, folks with persistent permissions should pin the
version of zope.dublincore == 3.6.0.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -