[Pkg-zope-developers] (no subject)

[Encolpe DEGOUTE]

Fabio Tranchitella a =E9crit :
> severity 297810 minor
> thanks
>=20
> For some strange reasons I missed this bug report because it hasn't bee=
n
> forwarded to my mailbox, sorry.
>=20
> When you have installed zope2.7 debian package, you have been warned
> about this and you have been adviced to symlink products for zope2.7
> instances, so this isn't a zope-cmfplone specific" ug.

I put one other on zope-cmf.
I just put the bug on them because with this system the maintainer of=20
zope-cps package and I cannot use CMF packages for CPS the we build it=20
in a all products in one package method. It's dirty.

> We are working to handle different zope versions (and different python
> versions) with only one product installation. I don't know if this will
> be included in sarge or not, but certainly we are taking care about thi=
s
> issue. All in all, this applies on almost all products and not only
> Plone.

It seems good.
I had done the work one year and a half ago but at that time nobody=20
cares of it.

> Il giorno mar, 08-03-2005 alle 13:27 +0100, martin f krafft ha scritto:
>=20
>>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.

Thanks :)

>>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.

Symlink is not a good idea. We use symlink for up-to-date products from=20
version control (cvs, svn or arch). For packaging products we have to=20
use more robust mecanism to protect instance about broken products on=20
upgrade. We can use python to manage this with a .ini file.

>>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!

Yes, discuss of these question here (pkg-zope-developpers). I do not=20
want to report more bugs on this but if I cannot see any discussion on=20
it, I will think zope maintainers work is dead again.

--=20
Encolpe DEGOUTE
http://encolpe.degoute.free.fr/
Logiciels libres, hockey sur glace et autres activit=E9s c=E9r=E9brales