Hello,
I think we should discuss and decide how to do the packaging of python
bindings for gtk+ 2.0 and GNOME 2. This because of namespace crash
between both gtk+ 1.2/2.0 bindings and GNOME 1.4/2.0 bindings. (When I
talk about the old bindings I mean python-gtk 0.6.9 and python-gnome
1.4.2. The new bindings are (the yet not in debian bindings) for gtk+
2.0 and GNOME2)
Just as reference:
-Today we only have bindings for Python 2.1 for gtk 1.2 and GNOME 1.4.
-The old bindings works with Python 2.2
-The new bindings will only work with Python 2.2 and newer.
These packages in main depend on python-gtk:
bonobo-python
gaby
gimp-python
glimmer
gnome-tasksel
iceme
icepref
pydict
pyne
python-configlet
python-gdk-imlib
python-glade
python-gnome
python-gtkextra
python-gtkglarea
python-twisted
scigraphica
scigraphica-gnome
solfege
sql-editor
These packages in main depend on python-gnome:
bonobo-python
eroaster
garchiver
gnome-tasksel
gramps
pgi
pybliographer
python-configlet
routeplanner-gnome
solfege
The big question is, should we be nice to programs using the old or the
new bindings? Two (maybe three) solutions exist.
===
1.
===
Be nice to old bindings. Let python-gtk 0.6.9 and python-gnome 1.4.2
live where they do how, and install the new python-gtk2 in
/usr/lib/pythonX.Y/site-package/gtk2/... and add
import sys
sys.path.insert(0, "/usr/lib/pythonX.Y/site-packages/gtk-2.0")
to all programs that use python-gtk2. And install python-gnome2 as
/usr/lib/pythonX.Y/site-packages/gnome2/ and add
import sys
sys.path.insert(0, "/usr/lib/pythonX.Y/site-packages/gnome2")
to all programs that use python-gnome2.
===
2.
===
Do exactly the opposite of above, and update all the packages that
depend on the old bindings. This way, program that are written for the
new bindings will find the bindings where upstream of python-gnome
install them.
===
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.
This way maintainers of packages that depend on the old bindings can
stay with python2.1 without changing the packages, or add
sys.path.insert if they update the packages to python2.2. And programs
that use python2.2-gtk2 and python2.2-gnome2 will run without changes on
debian.
===
4.
===
Please add..., there is probably something I have missed.
If we select #2, then I can do quite a lot of NMUs to make packages
installable if the maintainers don't have time.
I would prefer #2. I think #3 will add more confusion than it is worth.
Please comment.
--
Tom Cato Amundsen <[EMAIL PROTECTED]>
GNU Solfege - free eartraining, http://www.gnu.org/software/solfege/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
