TODO for zope2.12 package?
Gael Le Mignot
gael at pilotsystems.net
Thu Apr 28 10:02:51 UTC 2011
Hello Arnaud!
Wed, 27 Apr 2011 16:10:22 +0200, you wrote:
> Hi,
>>> Also, I have a question which may sound stupid though: how do you
>>> find out which Python modules to include directly into the
>>> tarball and the ones which should be put into Depends field? I
>>> thought it might be related to comments in the buildout recipes
>>> where it is stated which module APIs are not backward compatible
>>> anymore and will break... Or is it by just comparing the versions
>>> in Debian and the buildout recipe, and if newer, then add them to
>>> the tarball after checking that it's not actually working? Any
>>> hint?
>> i think this is a change remaining to be done: as far as i
>> remember, we decided to not use any packaged zope eggs at all, but
>> use local copies in the zope2.12 orig tarball instead for all of
>> them. i guess that the variable DEB_SATISFIED in debian/rules
>> controls, which zope eggs are fetched by get-orig-source, and
>> which are excluded. this whole exclusion code is not required if
>> we use local copies of _all_ eggs. thus michaels scripts unter
>> debian/build-scripts can be simplified a lot.
> By _all_ eggs, you mean only the Zope eggs, or even third-party
> dependencies such as ClientForm and mechanize for examples? The former
> solution may break at some point though...
For third-party modules (not inside the ztk or zope itself) we should
use system packages (the existing .deb) as much as possible,
IMHO. That's part of the goals of using .deb for Zope instead of
buildout : using the system python libraries.
--
Gaël Le Mignot - gael at pilotsystems.net
Pilot Systems - 9, rue Desargues - 75011 Paris
Tel : +33 1 44 53 05 55 - www.pilotsystems.net
Gérez vos contacts et vos newsletters : www.cockpit-mailing.com
More information about the pkg-zope-developers
mailing list