Remove conditional dependencies on non-existant zope-versions due dh_installzope

Stefan Huehner stefan at huehner.org
Wed Dec 20 14:09:53 UTC 2006


Hi,

i've notivced that several zope-packages specify conditional
dependencies on i.e. zope2.8 which is not (any longer) in the archive.

Some digging reveals that these deps are written by dh_installzope based
on a version-list included in this script and the information from the
'debian/dzprodudct':Zopeversions fields of each package.

To remove these dependencies two steps seem to be necessary:
1.) reduce the zope_versions list to the actually available
zope-versions
2.) reduce the ist in dzproduz:Zopeversions (in each packages) to the actually avaiable zope-versions, if the versions are explicitely defined there (i.e. '2.9 2.8').

The first step eliminates the dependency, when the '>=' syntax in
dzproduct is used or no ZopeVersions is specified at all.
The second one is necessary for the case where dzproduct explicitely list the versions as these are then directly used to the resulting dependencies.

A possible patch for step one is attached to this mail.

I'm happy for any feedback on these thougths before creating more
patches and creating bugs.

Regards,
Stefan

-------------- next part --------------
--- dh_installzope.orig	2006-12-20 14:49:51.000000000 +0100
+++ dh_installzope	2006-12-20 14:50:06.000000000 +0100
@@ -95,7 +95,7 @@
 
 init();
 
-my @zope_versions = ('2.6', '2.7', '2.8', '2.9', '2.10', '3');
+my @zope_versions = ('2.9', '2.10', '3');
 my %python_versions = ('3', '2.4');
 
 sub read_dzfile {


More information about the pkg-zope-developers mailing list