[Pkg-zope-developers] zope 2.7 questions

[A Mennucc]

--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


hi

with this e-mail, I hope to  start a discussion that will=20
lead to introduction of zope2.7 into Debian; here are some
troublesome points

1) my wish would be to build a package by the name zope2.7=20
 that installs into  /usr/lib/zope2.7 /var/lib/zope2.7

 There is a good reason for this: zope 2.7  is not considered=20
 yet stable enough by people doing commercial work (I was told by friends
 working in such a company); so I would not replace the package 'zope'
 that is now in Debian with a 'zope' of version 2.7

 This '/usr/lib/zope2.7' has though
 a problem with zope-* products, that usually install into  /usr/lib/zope

 1a) A solution would be to append   /usr/lib/zope/lib/python=20
 at the PYTHONPATH : this may lead into problems, since zope
 would see two copies of zope base products : I seem to=20
 remember that in this case Zope fills the log with=20
 " I see another copy of product blah blah...."

 1b)  A better solution would be to change the products:=20
 we may add into the zope-policy this idea:
 "any product that works with any version of zope available in Debian
  (possibly by autodetecting needed changes)
  installs into   /usr/lib/zope=20
  Otherwise it should install into /usr/lib/zope2.6 or /usr/lib/zope2.7 "

 Them we  change 'zope' to install into  /usr/lib/zope2.6=20
=20
  zope 2.6 would have  PYTHONPATH=3D/usr/lib/zope2.6:/usr/lib/zope

  zope 2.7 would have  PYTHONPATH=3D/usr/lib/zope2.7:/usr/lib/zope

  We may even have a virtual package 'zope' and have packages=20
  'zope2.6' and 'zope2.7'=20

  I like this idea best: for example, we may have both plone1 and plone2
  in Debian

  if you like the idea, we implement it and add to experimental

2) zope 2.7  eases up a lot   creation and management of multiple instances=
,=20
  (and my package contains an extra script to help admins)

  this instances are quite cool.... but are not FHS compliant:
  any instance contains its own 'etc' 'var' 'bin' and 'log'

  I would not move 'bin' which contains bin/runzope bin/zopectl
  that start/stop that particular instance; and similarly 'etc'

  'var' can stay where it is

  maybe it is possible to move away 'log': for example
  we may move  /var/lib/zope/instance/XXX/log   to
  /var/log/zope/XXX

  what do  you think?

3) packages of  zope  are not FHS compliant:
 they contain everything into /usr/lib/zope (but for docs, that
 are moved or linked into /usr/share/doc

 my package of zope2.7 does this , as well as  zope_2.6.4-1.1_i386.deb AFAI=
CT

 I personally don't think that making zope FHS-compliant
 is worth the effort... it would break too many things!
  and you?

a.

--=20
Andrea Mennucc
 "one houndred and fifty - the chicken sings"
--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAh4DC9B/tjjP8QKQRAlc9AJ9puNFovCDovjnAMFNyNdbgFvSIYACfdl/F
qqKyzLPmqxqB+XdrlHowx6g=
=aSmp
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--