Re: Using python + pygtk in Desktop modules (was Re: Revisitingthe Gnome Bindings)
- From: Ross Burton <ross burtonini com>
- To: Sean Middleditch <elanthis awesomeplay com>
- Cc: GNOME Desktop Devel List <desktop-devel-list gnome org>
- Subject: Re: Using python + pygtk in Desktop modules (was Re: Revisitingthe Gnome Bindings)
- Date: Tue, 28 Sep 2004 15:29:29 +0100
> No packaging system that I am aware of handles situations like Python's
> (or the kernels, or GStreamer's, or any other framework's) either.
> Namely, say you have the framework package of a particular version
> installed; python-2.3. And then you have a versioned library installed
> for this framework; say, pygtk-2.3-2.4. (pygtk 2.4 for python 2.3) Now
> an upgrade of python comes along to 2.4. The system should see that to
> install python 2.4, you need the matching pygtk-2.4-2.4 package in order
> to make sure all apps keep working. No packaging system can do this,
> however. Just like pretty much every packaging system will let you
> upgrade your kernel without requiring you to upgrade any drivers you
> have installed, potentially going so far as to cause the new kernel to
> not even boot.
Sounds like the Debian python packaging policy to me.
For example, python2.3 is the interpreter, python2.3-gtk2 is the GTK+
bindings. Add a number of meta packages for the default version of
python ("python" deps on python2.3, python-gtk2 on python2.3-gtk2, etc)
and you have applications which can depend on "python, python-gtk" and
carry on working as python is upgraded.
Ross
--
Ross Burton mail: ross burtonini com
jabber: ross burtonini com
www: http://www.burtonini.com./
PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]