Re: Bug#302295: python should use the alternatives mechanism
Ralph Giles writes: > On Sun, Apr 03, 2005 at 03:44:47PM +0200, Matthias Klose wrote: > > > no, because you cannot assure, that all modules installed in one > > version are installed on the other version as well. > > So because debian packages don't track python module dependencies > correctly, incorrect. if there's such a package, please file a bug report. > I must write my scripts to hardwire the specific name of > debian's versioned python? if you want to use a python version, which is not the default one, yes. > How does that fulfill the social contract? sorry, the social contract doesn't tell anything about screwing about your system. > Even if alternatives isn't appropriate, some mechanism is needed. > There must be some way to tell the packaging system which python > one wants by default, and hand-editing a symlink after every upgrade > is just wrong. correct, that's wrong. call the specific version in this case. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302295: python should use the alternatives mechanism
Ralph Giles writes: > On Sun, Apr 03, 2005 at 08:54:58PM +0200, Matthias Klose wrote: > > > > > no, because you cannot assure, that all modules installed in one > > > > version are installed on the other version as well. > > > > > > So because debian packages don't track python module dependencies > > > correctly, > > > > incorrect. if there's such a package, please file a bug report. > > Ok, I must have misunderstood. If the python packages used the > alternatives mechanism *and* tracked dependencies properly, why > is there any problem with what modules are installed? consider Package: baz Depends: python2.2 | python2.3, python2.2-foo | python2.3-foo, python2.2-bar | python2.3-bar the dependencies are fullfilled installing python2.2-foo and python2.3-bar... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302295: python should use the alternatives mechanism
On Sun, Apr 03, 2005 at 08:54:58PM +0200, Matthias Klose wrote: > > > no, because you cannot assure, that all modules installed in one > > > version are installed on the other version as well. > > > > So because debian packages don't track python module dependencies > > correctly, > > incorrect. if there's such a package, please file a bug report. Ok, I must have misunderstood. If the python packages used the alternatives mechanism *and* tracked dependencies properly, why is there any problem with what modules are installed? -r -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302295: python should use the alternatives mechanism
On Sun, Apr 03, 2005 at 09:21:55PM +0200, Matthias Klose wrote: > consider > > Package: baz > Depends: python2.2 | python2.3, python2.2-foo | python2.3-foo, > python2.2-bar | python2.3-bar > > the dependencies are fullfilled installing python2.2-foo and python2.3-bar... So how does package baz invoke python? and how does it know it got the right version? Thank you for the pointer (see the bug history) to the python policy. I understand where you're coming from better now. But you still seem to be saying the bug should be closed because the change it requests is counter to the policy *whose behavior the bug report is against*. That seems inappropriate to me. -r -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#302295: python should use the alternatives mechanism
On Sun, 2005-04-03 at 12:53 -0700, Ralph Giles wrote: > On Sun, Apr 03, 2005 at 09:21:55PM +0200, Matthias Klose wrote: > > > consider > > > > Package: baz > > Depends: python2.2 | python2.3, python2.2-foo | python2.3-foo, > > python2.2-bar | python2.3-bar > > > > the dependencies are fullfilled installing python2.2-foo and > > python2.3-bar... > > So how does package baz invoke python? and how does it know it got the > right version? package baz needs to decide what version it is going to work with first; Depends: python (>=2.2), python (<2.4), python-foo, python-bar the default version of python between >=2.2 and <2.4. should use /usr/bin/python Depends: python2.2, python2.2-foo, python2.2-bar python version 2.2 only. should use /usr/bin/python2.2 Depends: python2.3, python2.3-foo, python2.3-bar python version 2.3 only. should use /usr/bin/python2.3 If you wish to support all of these, then you need to create separate packages for each; python-baz, python2.2-baz, python2.3-baz. The only way it could do what you are suggesting is if dpkg supported dependencies like; Package: baz Depends: (python (>=2.2), python (<2.4), python-foo, python-bar) | (python2.2, python2.2-foo, python2.2-bar) | (python2.3, python2.3-foo, python2.3-bar) You could file a bug report (if there isn't already one) against dpkg, but do we really need it? We already support multiple versions of Python rather well... last time I looked we do it much better than any other distro. > Thank you for the pointer (see the bug history) to the python policy. I > understand where you're coming from better now. But you still seem to be > saying the bug should be closed because the change it requests is > counter to the policy *whose behavior the bug report is against*. That > seems inappropriate to me. It is fair enough to close a bug with a "wont fix" because it is a wishlist that is never going to be implemented... -- Donovan Baarda <[EMAIL PROTECTED]> http://minkirri.apana.org.au/~abo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
