Raphael Hertzog writes: > On Tue, 06 Jun 2006, Matthias Klose wrote: > > assume we want to add a python2.5 package. It's nice to have, but > > extensions will need an update, or they will FTBFS. At this point I > > would rather not see python2.5 as supported. > > Agreed, however it would be nice for package which do already work with > python2.5 to be able to provide that... > > > The 'Provides: python2.3-foo, python2.4-foo' is missing for all > > packages with private modules and scripts (without shared modules). > > For that case we do need XB-Python-Version. If we do want to drop the > > Provides for packages where they are not needed, we need it for shared > > modules as well. > > What for? Modules are automatically available to all python versions > (except those which do not support all versions, but then we can't do > better...).
please read again. I'm not talking about shared modules. > > > Don't you think this new field and Provides are redondant, and that you > > > could decide which rebuilds are necessary from it ? > > > > no, not for packages with private extensions. ... or private modules. > Does this kind of package exist? (ie do you have an example?) i.e. zope2.x we have to keep that information for packages with private modules using a non-standard version of python as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
