python-gtk and python-gtk2 (and gnome packages), please comment
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]
RE: python-gtk and python-gtk2 (and gnome packages), please comm
> > === > 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. > why is this so messy? You only compile for one python version and you match the upstream in either case. The existing software works perfectly without change in both cases. Seems like everyone wins here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: python-gtk and python-gtk2 (and gnome packages), please comment
On Sat, 2002-06-22 at 00:07, Tom Cato Amundsen wrote: > Hello, > === > 4. > === > Please add..., there is probably something I have missed. Now I remember what #4 was: Let both python2.2-gtk and python2.2-gtk2 install into /usr/lib/python2.2/site-packages, and let the packages conflict with each other. -- 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]
RE: python-gtk and python-gtk2 (and gnome packages), please comm
On Sat, 2002-06-22 at 00:08, Sean 'Shaleh' Perry 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. > > > > 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. > > > > why is this so messy? You only compile for one python version and you match > the upstream in either case. The existing software works perfectly without > change in both cases. Seems like everyone wins here. > Ok, not messy, but the most "complicated", since programs that depend on python2.1-gtk need no change, but if they depend on python2.2-gtk, they need an sys.path.insert. Maybe this is the best. Thats why I would like to hear peoples opinion. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- 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]
RE: python-gtk and python-gtk2 (and gnome packages), please comm
>> >> why is this so messy? You only compile for one python version and you match >> the upstream in either case. The existing software works perfectly without >> change in both cases. Seems like everyone wins here. >> > > Ok, not messy, but the most "complicated", since programs that depend on > python2.1-gtk need no change, but if they depend on python2.2-gtk, they > need an sys.path.insert. Maybe this is the best. Thats why I would like > to hear peoples opinion. > it is not that harsh to simply limit python apps using gtk 1.2 to python version 2.1. If they want to move up to 2.2 (or higher) they have to port to gtk 2.0. that is my opinion anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: python-gtk and python-gtk2 (and gnome packages), please comm
On Fri, Jun 21, 2002 at 03:16:24PM -0700, Sean 'Shaleh' Perry wrote: | >> why is this so messy? You only compile for one python version | >> and you match the upstream in either case. The existing software | >> works perfectly without change in both cases. Seems like | >> everyone wins here. | > | > Ok, not messy, but the most "complicated", since programs that depend on | > python2.1-gtk need no change, but if they depend on python2.2-gtk, they | > need an sys.path.insert. Maybe this is the best. Thats why I would like | > to hear peoples opinion. | | it is not that harsh to simply limit python apps using gtk 1.2 to python | version 2.1. If they want to move up to 2.2 (or higher) they have to port to | gtk 2.0. This sounds acceptable to me. -D -- Bugs come in through open windows. Keep Windows shut! http://dman.ddts.net/~dman/ pgpQCMWVWI8yt.pgp Description: PGP signature
