Development for wheezy

[Jonas Meurer]

On 10/03/2011 Brian Sutherland wrote:
> > > The current plan is to only have one version of the ZTK packaged at a
> > > time. Basically by only uploading the python-zope.* versions that
> > > correspond to the ZTK version we want to package.
> > > 
> > > We may deviate (very slightly) from the ZTK for bugfixes.
> > > 
> > > I'm planning to make some time in the near future to prepare packages
> > > that correspond to the ZTK 1.1.
> > 
> > That would break Zope2.13 packages which depend on the python-zope.*
> > packages in Debian, as backwards compability is not warranted for
> > differnt major ZTK versions (e.g. 1.0 and 1.1).
> 
> I see, and for you guys, the ability to have more than one version of
> Zope2 installed at the same time is a killer feature?

I would prefer to keep this ability, yes. Migration from one major Zope2
version to another is not always easy. Thus it's much easier for admins
to have several Zope2 versions installed in parallel. That way they can
migrate their applications one by one.

> Yeah, in that case you can't depend on the python-zope.* packages till
> python packaging in debian sanely allows more than one library version
> installed at a time.
> 
> Which is probably not gonna happen soon. Pity.
> 
> Thanks for taking the time to work through this, but I guess I finally
> understand where the real problem is.

Even with only one Zope2 version in the archives, I guess the situation
would be far from perfect. Migration from one major ZTK release to
another one would be a huge coordination experiment, as all seperate
packges would need to be updated at once, along with the Zope2 package.

Additionally loads of Conflicts and/or Breaks would be required to
prevent conflicting versions to be installed together (e.g. Zope2.13 and
packages from ZTK 1.1).

Maybe a python-zope.ztk1.0 (python-zope.ztk1.1) metapackage could be
introduces, which the Zope2 erver package depends on. And this
metapackage depends on particular versions of the ZTK components.

To be clear: I really would appreciate a solution where python-zope.*
packages are used by the Zope2 server package. But I don't see a good
solution so far.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20110310/f03958d6/attachment.pgp>