On Sat, Jun 22, 2002 at 12:07:19AM +0200, Tom Cato Amundsen wrote: > === > 3. > === > Quite messy, but... > Since python-gtk2 require python2.2 or later, we let python2.1-gtk > install as upstream does (in /usr/lib/python2.2/site-packages/) and > install python2.2-gtk in /usr/lib/python2.2/site-packages/gtk1.2/. And > python2.2-gtk2 can install as upstream does in > /usr/lib/python2.2/site-packages.
That's probably the only way we can go. I don't expect that any
upstream tool will user "import gtk2" or something as upstream
kept the module name "gtk". So basically I think we don't have a choice.
Of course if consensus is different from my opinion I'll go out of
the way ;)
Reading your mail for real again (it's late) you got a point. #2 would
be the right thing to do (tm) I think. There is still time to go
that route. But - do we want to continue supporting the old gnome
for sarge? Otherwise I would be for removing the old binding
entirely before the next release. Just wondering if any dependent
package will be updated for the new gnome.
cu
Torsten
pgpDSTRWGkP5b.pgp
Description: PGP signature
