severity 297810 important thanks I agree that this is a bug, but it's no more than an important bug because it does not render the package unusable to everyone, just those using Zope2.7. In fact, I am not even sure whether this isn't just a plain wishlist bug.
Anyway, my suggested fix would be to install Plone products to /usr/share/plone/Products, and then to symlink them individually to the two Zope hierarchies. However, this fails when the two Zope instances use different Python versions (which they do), because of pre-compiled modules. Thus, short of installing plone twice, I do not see an easy way out. Maybe then it would be possible to filter out common stuff into plone-common. Note that I copied the Debian Zope developers list. I hope they have already worked out a policy for this. Otherwise we will need to get thinking about one soon! -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
signature.asc
Description: Digital signature
