In the past, gconf-sharp-2.16.0 was able to be built with gtk-sharp-2.12, but, later, this was dropped forcing users (like me) that want to use latest banshee or f-spot to install a lot of gnome-2.24 stuff 25 Nov 2008; Peter Alfredsen <loki_val@gentoo.org> gconf-sharp-2.16.0.ebuild: No easy transition for this package, it seems, dependencies are conflicting. I mailed to Peter Alfredsen about what conflicts were occurring and he replied me that there were problems because ebuild was installing a gtk-sharp version and eclass was asking for a different one. I rode gtk-sharp-component.eclass and saw that ECLASS_DEPENDS="no" can be exported for letting ebuild to handle dependencies: # Make sure we're building with the same version. [[ "${ECLASS_DEPENDS}" = "no" ]] || DEPEND="=dev-dotnet/gtk-sharp-${GTK_SHARP_REQUIRED_VERSION}* >=sys-apps/sed-4" then, I attach a diff to be applied to gconf-sharp-2.16.0.ebuild for making enough changes for allowing it to be built against newer gtk-sharp solving this problem Thanks Reproducible: Always
Created attachment 175133 [details] gconf-sharp-2.16.0.ebuild.diff
Doing that would create conflicting dependencies. All of the gtk-sharp-component packages must be built with the same gtk-sharp or there will be runtime errors. This is a consequence of the fact that they're all derived from the same tarballs. If you want to use ~arch packages, you will be forced to use ~arch deps. Sorry.
OK, sorry for the inconvenience
