<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] libgsf 1.14.23: no python by default
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20libgsf%201.14.23%3A%20no%20python%20by%20default&In-Reply-To=%3C20120420080831.GB12808%40bkor.dhs.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="014543.html">
<LINK REL="Next" HREF="014545.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] libgsf 1.14.23: no python by default</H1>
<B>Olav Vitters</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20libgsf%201.14.23%3A%20no%20python%20by%20default&In-Reply-To=%3C20120420080831.GB12808%40bkor.dhs.org%3E"
TITLE="[Mageia-dev] libgsf 1.14.23: no python by default">olav at vitters.nl
</A><BR>
<I>Fri Apr 20 10:08:31 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="014543.html">[Mageia-dev] [changelog] [RPM] cauldron core/release ocaml-extunix-0.0.3-2.mga2
</A></li>
<LI>Next message: <A HREF="014545.html">[Mageia-dev] libgsf 1.14.23: no python by default
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14544">[ date ]</a>
<a href="thread.html#14544">[ thread ]</a>
<a href="subject.html#14544">[ subject ]</a>
<a href="author.html#14544">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>In just released libgsf (1.14.23), Python is not built by default.
Quoting <A HREF="https://bugzilla.gnome.org/show_bug.cgi?id=672663:">https://bugzilla.gnome.org/show_bug.cgi?id=672663:</A>
|<i> The python bindings depends in pygtk-codegen-2.0 which is now a wrapper
</I>|<i> for pygobject-codegen-2.0 which itself was removed from pygobject.
</I>|<i> Instrospection being available they are obsolete either way.
</I>|<i>
</I>|<i> This patch disable their generation by default.
</I>
What to do with above? By default python support is not built anymore
due to above. I can enable it in configure again, but prefer to just not
build it (despite above, still compiles with --with-python). If
something needs libgsf, they should use gobject introspection (which you
can use from Python as well as js, etc).
Nothing seems to depend on python-libgsf AFAICS
Should I:
- disable for Mageia 2 (as nothing seems to require python-libgsf)
should I add a Obsolete and where? task-obsolete or libgsf itself?
- enable static python bindings only for Mageia 2, remove after
in case something actually requires it
- stay with current libgsf version
problem sounds generic though, would apply to previous as well
--
Regards,
Olav
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="014543.html">[Mageia-dev] [changelog] [RPM] cauldron core/release ocaml-extunix-0.0.3-2.mga2
</A></li>
<LI>Next message: <A HREF="014545.html">[Mageia-dev] libgsf 1.14.23: no python by default
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14544">[ date ]</a>
<a href="thread.html#14544">[ thread ]</a>
<a href="subject.html#14544">[ subject ]</a>
<a href="author.html#14544">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>