Summary: | compilation program with x11-libs/gtksourceview:2 fails if G_DISABLE_DEPRECATED is defined | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey Ilinykh <rion4ik> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey Ilinykh
2011-12-16 12:19:21 UTC
Are there any ebuilds in portage that fail as a result of G_CONST_RETURN in gtksourceview:2 headers, or does this only affect users who are doing their own software development? I dunno. I tried to compile my own if more exactly its not mine. its gmanedit from my overlay The reason for my question is that ebuilds in portage should not be building with -DG_DISABLE_DEPRECATED. It is a useful tool for upstream developers of a package to make sure that they are using the latest glib API, but for average end users it only causes mysterious build failures after glib updates.
Fixed in 2.10.5-r2.
>*gtksourceview-2.10.5-r2 (17 Dec 2011)
>
> 17 Dec 2011; Alexandre Rostovtsev <tetromino@gentoo.org>
> +gtksourceview-2.10.5-r2.ebuild,
> +files/gtksourceview-2.10.5-G_CONST_RETURN.patch:
> Add patch from gtksourceview-3.x to not use G_CONST_RETURN in public headers
> (bug #394925, thanks to Rion for reporting).
thanks for notice. I'll consider it next time (In reply to comment #3) > if more exactly its not mine. its gmanedit from my overlay Also would be interesting to let gmanedit developers they shouldn't release stable tarballs with *DISABLE_DEPRECATED* flags used by default, they are oriented to development purposes ;) |