On Wed, 14 Jun 2006, Pierre Habouzit wrote: > let's imagine we have that case: > > python-foo is a python module that uses and needs features from > python2.X. python-bar uses python-foo but can work with all 2.* python > version. > > Python-Versions will be: > * >= 2.X for python-foo > * all for python-bar > > how do we ensure that a user that has a python 2.Y installed, Y < X will > not been able to install python-bar without also pulling python2.X ?
python-foo will depend on 'python (>= 2.X)'. When you install python-bar, python-foo is installed and its dependencies must be satisfied. This means that python package will be upgraded to 2.X which will install python2.X. > Is there anything planned to address that ? No, the case you describe is not broken. :-) (The policy is not perfect, you'll find another challenging problem for us I'm sure. :-)) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
