[Pkg-zope-developers] Re: [Zope] A few questions...

A Mennucc mennucc1@debian.org
Thu, 17 Feb 2005 11:46:05 +0100


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


sorry, I do not use and know ZEO well enough to help

I am sending a copy of this to the list: some people there use ZEO

a

On Wed, Jan 26, 2005 at 10:23:24AM -0700, Joel Aelwyn wrote:
> On Wed, Jan 26, 2005 at 10:13:04AM +0100, Fabio Tranchitella wrote:
> > Il giorno mar, 25-01-2005 alle 15:33 -0700, Joel Aelwyn ha scritto:
> > > [ Mail-Followup-To set; please *do* Cc me, as I do not currently     =
     ]
> > > [ subscribe to the -python list, though it appears to be the proper p=
lace ]
> > > [ for Zope discussions, at least from what I can find in the archives=
.    ]
> > > [ Please redirect me if somewhere else is more appropriate.          =
     ]
> > >=20
> > > So I have relatively recently taken over a Zope package, and while it=
 is
> > > now in (basically) good shape, there are a couple of technical points=
 I
> > > want to clear up to make sure I'm doing it right, since what I can fi=
nd on
> > > the mailing list archives isn't entirely conclusive.
> >=20
> > I think the right place for your email is the mailing list of zope
> > debian packages developers [1], but the list seems to be almost dead.
>=20
> Allright.
>=20
> > > 1) Is it proper (assuming that the package works under both Zope 2.6 =
and
> > >    Zope 2.7) to Depend on 'zope | zope2.7'? It seems like it should b=
e, but
> > >    I wanted to double-check.
> >=20
> > IMHO the dependency should be "zope2.7 | zope", so the newer version
> > will be automatically installed if needed.
>=20
> Hmmm. I got the (quite possibly mistaken) impression that the 'zope2.7'
> package was intended as a temporary situation, rather than 'zope' being
> permanently stuck at 2.6 and all future Zope packages adding a new source
> package. I mean, I could see 'Zope3', given that a major revision is
> allowed to break all sorts of things, but why split 2.7 into a separate
> package?
>=20
> > > 2) Usage of debconf templates. The debconf manual (and the maintainer)
> > >    seem to think that every package which uses the shared Zope restart
> > >    template needs to provide an identical copy.=20
> >=20
> > My opinion on this issue is that for zope packages you do not use the
> > shared template, just read its value in debian/postinst. For this
> > reason, you haven't (and you shouldn't) provide the template: you'll
> > never ask the user for that question so providing the template have
> > really no sense, this just create additional work for the translators.
> >=20
> > Here an example from one of my packages:
> >=20
> > $ cat zope-cmfphoto-0.5.0/debian/postinst | grep "shared/zope"
> >         db_get "shared/zope/restart" || true
> >=20
> > If db_get fails (the package zope isn't installed, or the template
> > hasn't been initialized, or something else) the "or true" prevents the
> > maintainer script to return a bad exit code.
>=20
> Believe me, I understand the rationale. My issue is that this rationale
> isn't, formally, supported by debconf. So I guess I should CC it to the
> debconf maintainer for clarification.
>=20
> > So, why for the hell you provide the template in your package? :)
>=20
> Solely because "that's the requirement according to the debconf manual
> and maintainer".
>=20
> > After this, I maintain a lot of zope packages. Packaging this type of
> > software is quite easy, and often it is a repetitive job. For this
> > reason I'd like to see a dh_zope debhelper script, so the packages=20
> > (at least the easy ones) could get rid of their templates and their
> > maintainer scripts. I know that Luca De Vitis started working on it,=20
> > and I tried to mail him but I haven't received any answer so far.=20
> > His last upload to zope package is on 2004, February. Does anyone=20
> > know if he is still around?
>=20
> No argument here; some sort of dh_zope would be very handy, given that mo=
st
> of the "weird" bits of packaging I had to do were Zope specific (things
> like symlinks to move static images out of /usr/lib, or dealing with the
> debconf stuff) that could easily be wrapped up in a dh_zope utility.
> --=20
> Joel Aelwyn <fenton@debian.org>                                       ,''=
`.
>                                                                      : :'=
 :
>                                                                      `. `'
>                                                                        `-



--=20
Andrea Mennucc
 "Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef"

--SUOF0GtieIMvvwua
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCFHXt9B/tjjP8QKQRArQ+AJwIVZzwLreCh4TN3Zxz0qvIk+S3pACeMiKJ
UlDnGj1pIfuSIzubst8+KJg=
=sPDf
-----END PGP SIGNATURE-----

--SUOF0GtieIMvvwua--