Since the graph feature in transmission-remote-gtk doesn't work with gtk3, I'd like to request a gtk3 USE flag, so we can have the graph until its issues with gtk3 are resolved upstream. Reproducible: Always
Created attachment 317308 [details] transmission-remote-gtk-1.0.2.ebuild with gtk3 USE flag
Comment on attachment 317308 [details] transmission-remote-gtk-1.0.2.ebuild with gtk3 USE flag --- transmission-remote-gtk-1.0.2.ebuild 2012-07-04 10:15:33.000000000 +0200 +++ - 2012-07-05 17:14:16.515976451 +0200 @@ -12,17 +12,17 @@ LICENSE="GPL-2" SLOT="0" KEYWORDS="~amd64 ~x86" -IUSE="ayatana debug geoip libproxy" +IUSE="ayatana debug geoip gtk3 libproxy" RESTRICT="test" RDEPEND=">=dev-libs/glib-2.28 >=dev-libs/json-glib-0.12.6 net-misc/curl - x11-libs/gtk+:3 >=x11-libs/libnotify-0.7 ayatana? ( dev-libs/libappindicator:3 ) geoip? ( dev-libs/geoip ) + gtk3? ( x11-libs/gtk+:3 ) !gtk3? ( >=x11-libs/gtk+-2.21.1:2 ) libproxy? ( net-libs/libproxy )" DEPEND="${RDEPEND} dev-util/intltool @@ -34,7 +34,7 @@ src_configure() { econf \ $(use_enable debug) \ - --enable-gtk3 \ + $(use_enable gtk3) \ $(use_with geoip libgeoip) \ $(use_with libproxy) \ $(use_with ayatana libappindicator)
According to bug #420493, we should all be moving /away/ from using IUSE=gtk3.
I somewhat agree with Alexandre here. Gtk3 support should never have been conditionally enabled by default if ANY features are missing compared to gtk2. That is the official policy of the GNOME team so until upstream makes the graph work on gtk3, gtk2 should be used.
Is any of this still relavent with the version 1.1? The GTK+-3 GUI works _great_ here with 1.1.
(In reply to comment #5) > Is any of this still relavent with the version 1.1? The GTK+-3 GUI works > _great_ here with 1.1. Yes, the graph feature is still disabled for gtk3.
Checking up on this, the author branched 1.0.2 to experiment on fixing the graph on gtk3, but it appears completely forgotten for the past 2 years. I rather like the feature but don't know how to fix it, so I'll stick with my gtk2 1.0 version for now. And since nobody else seems to care for it, especially upstream, I think better to close this than to leave it on limbo. Thanks for the attention. =)