RFH: gi and overrides, how it should be packaged

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

RFH: gi and overrides, how it should be packaged

Osamu Aoki
Hi gnome folks,

The input method packaging team is wondering what to do with the
/usr/lib/python*/dist-packages/gi/overrides/Ibus.py files generated when
python-gi-dev is in the build environment.

Do we make python-ibus just for them?  Or put it inside gir* packages.

I have no idea which one is better.  (gir* is easier for me...)

See more as below and let us know your thought.

On Sun, Jul 20, 2014 at 06:04:44PM +0900, Changwoo Ryu wrote:

> 2014-07-20 (일), 15:18 +0900, Osamu Aoki:
> ...
> > In debian speak, this is something like ibus-py2override package.
> >
> > I have no idea if this is required by some packages on Debian.  So far,
> > I have not seen one.  Does any one have idea?
> >
> > Also, overrides under python3 side are not packaged.
> >
> > Changwoo, do you have any use for installing thise files?
>
> In general, those g-i "overrides" provide additional or modified APIs
> when automatically generated g-i bindings are not enough. For example
> when automatic bindings don't look good in Python. And they are
> transparent; you don't have to specify explicitly to use the overridden
> code.
>
> So when the ibus g-i overrides are installed, the ibus programs in
> Python transparently use them. But interestingly, all ibus Python
> programs in Debian seem to work without the overrides.
>
> I still think the overrides should be installed, because they are the
> officially provided ibus Python APIs anyway.
>
> In Debian, the g-i overrides are packaged in python-* packages or
> sometimes in gir* packages. I have no idea which one is better.
>
> $ apt-file search /gi/overrides/
> gedit: /usr/lib/python3/dist-packages/gi/overrides/Gedit.py
> gir1.2-dee-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/Dee.py
> gir1.2-dee-1.0: /usr/share/pyshared/gi/overrides/Dee.py
> gir1.2-gexiv2-0.10: /usr/lib/python2.7/dist-packages/gi/overrides/GExiv2.py
> gir1.2-gexiv2-0.10: /usr/lib/python3/dist-packages/gi/overrides/GExiv2.py
> gir1.2-grip: /usr/lib/python2.7/dist-packages/gi/overrides/Grip.py
> gir1.2-grip: /usr/lib/python3/dist-packages/gi/overrides/Grip.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GIMarshallingTests.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GLib.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/GObject.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gdk.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gio.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/Pango.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/__init__.py
> python-gi: /usr/lib/python2.7/dist-packages/gi/overrides/keysyms.py
> python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/Gst.py
> python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/GstPbutils.py
> python-gst-1.0: /usr/lib/python2.7/dist-packages/gi/overrides/_gi_gst.so
> python-gst-1.0-dbg: /usr/lib/python2.7/dist-packages/gi/overrides/_gi_gst_d.so
> python-v-sim: /usr/lib/python2.7/dist-packages/gi/overrides/v_sim.py
> python-v-sim: /usr/share/pyshared/gi/overrides/v_sim.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GIMarshallingTests.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GLib.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/GObject.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gdk.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gio.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Gtk.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/Pango.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/__init__.py
> python3-gi: /usr/lib/python3/dist-packages/gi/overrides/keysyms.py
> python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/Gst.py
> python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/GstPbutils.py
> python3-gst-1.0: /usr/lib/python3/dist-packages/gi/overrides/_gi_gst.cpython-34m-x86_64-linux-gnu.so
> python3-gst-1.0-dbg: /usr/lib/python3/dist-packages/gi/overrides/_gi_gst.cpython-34dm-x86_64-linux-gnu.so
> $
>
>
>
> Regards
>
> Changwoo
>
>


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: https://lists.debian.org/20140720170752.GA7624@goofy

Reply | Threaded
Open this post in threaded view
|

Re: RFH: gi and overrides, how it should be packaged

Josselin Mouette
Hi Osamu,

Le lundi 21 juillet 2014 à 02:07 +0900, Osamu Aoki a écrit :
> Hi gnome folks,
>
> The input method packaging team is wondering what to do with the
> /usr/lib/python*/dist-packages/gi/overrides/Ibus.py files generated when
> python-gi-dev is in the build environment.
>
> Do we make python-ibus just for them?  Or put it inside gir* packages.
>
> I have no idea which one is better.  (gir* is easier for me...)

Since they are overrides for modules which are loaded through GI, it
looks much better to put them in the gir* package.

Cheers,
--
 .''`.      Josselin Mouette
: :' :
`. `'
  `-


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: https://lists.debian.org/1406394599.2376.6.camel@tomoyo