On Tue, Jun 13, 2006 at 08:17:17AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Tue, Jun 13, 2006 at 01:49:26AM +0200, Matthias Klose <[EMAIL PROTECTED]> > wrote: > > - The current pythonX.Y-foo packages having modules in the python > > library path are collapsed into one package python-foo. Binary > > independent modules are made available for the python versions > > currently supported in the distribution. Binary dependent > > extensions are put for all supported python versions into the > > same python-foo package. The overhead for a maybe unused > > extension module was accepted in favour of a reduction of > > packages, the removed need to rebuild a package for a change > > of the default python version and less NEW processing when > > adding support for a new pythonX.Y version. > > Will /usr/lib/python2.x/site-packages be ignored by dh_shlibdeps as part > of this master plan ?
Which would be stupid, Mike, thank you. Don't sent mail when you're still not awake. Anyways, there would be a problem with python native extensions linked against libpython. They would get the shlib dependencies on python2.x packages. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
