Quoting Neil Schemenauer <[EMAIL PROTECTED]>: > Donovan Baarda wrote: > > Hmmm, but if only "python" can provide python-api-*, then any packages > that > > depend on python-api-X.Y will be broken when a new version of python > > providing python-api-X.Z comes out, and no python-X.Y package can be > > compatible with it. > > That's right. Packaged modules must be updated when a new version of > Python is installed.
That make this an "Option 1" policy. That's fine, as long as you recognise it as such. The option of creating python-X.Y packages for older versions is a bit of a non-feature... who in their right mind is going to re-package old versions of python and all their support modules? Why would you bother? You might as will update just the bits you want for the new Python. Just to make it clear... the new python package will be unusable for everyone until _all_ the python packages they use have been upgraded. The alternative is when a python-X.Y has been released and all the packages they use have been re- relases as python-X.Y-foo packages. Note that is also means that no packages that depend on the new python can be installed or upgraded untill all the python package you use have been upgraded... you want to install gnumeric... that uses python (2.1)... you also use python-obscurewigit, sorry that uses python (1.5). It hasn't been upgraded yet, and probably won't be for a while because it is unsupported, so you can't upgrade python. Your options are; create your own upgraded python-obscurewigit package, or re-package python (1.5) and all it's modules, including python- obscurewigit, as python-1.5 packages. I guess this will encorage people to update their packages :-) -- ABO: finger [EMAIL PROTECTED] for more information.
