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]
