Torsten Landschoff <[EMAIL PROTECTED]> wrote:
> Problem with this: No matter which python-gnome release shall be used
> the upstream will use "import gnome.ui". So which binding should he
> get?
Yes, this is problematic. The question "Why not having gtk2, gnome2,
etc. modules instead of gtk, gn
On Wed, Aug 07, 2002 at 11:09:33AM +0200, Florent Rougon wrote:
> > 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
Hi,
Torsten Landschoff <[EMAIL PROTECTED]> wrote:
> 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.
O
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-
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
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
6 matches
Mail list logo
