Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 392571 - please restore www-client/midori-0.4.2 (for it has GTK-2 support)
Summary: please restore www-client/midori-0.4.2 (for it has GTK-2 support)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: XFCE Team
URL:
Whiteboard:
Keywords:
: 396055 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-30 08:20 UTC by Balint SZENTE
Modified: 2011-12-27 16:05 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Balint SZENTE 2011-11-30 08:20:09 UTC
The midori-0.4.2.ebuild was removed from portage with the following message: "old".

I think this is inappropriate. The latest version of Midori is 0.4.2 and primarily GTK-2 is supported. GTK-3 support is only experimental:

"Support for GTK+3 is still considered experimental and not recommended for daily use. Build with --enable-gtk3 --disable-addons to try it out."

Please, undo the removal of this ebuild. I think a lot of people are using Midori with GTK-2 support, especially that Xfce is still with GTK-2.

Reproducible: Always
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2011-12-06 03:51:33 UTC
only temporarily... next version will not have gtk+-2.x ebuild anymore. get used to the gtk+-3.x migration. use theme that has both gtk+-2.x and gtk+-3.x support, such as greybird (x11-themes/greybird) or zukitwo (x11-themes/zukitwo).

+  06 Dec 2011; Samuli Suominen <ssuominen@gentoo.org>
+  +midori-0.4.2-r200.ebuild:
+  Restore GTK+ 2.x based ebuild for now wrt #392571 by Balint SZENTE
Comment 2 Balint SZENTE 2011-12-06 08:23:20 UTC
Thanks for putting back the ebuild.

Actually, it's not about getting used with GTK-3. I see two main problems here:

 1 . If the author of the program states that Midori is not recommended for daily usage with GTK-3 (and I use Midori as default browser), than I would prefer to stick with GTK-2 at least until the GTK-3 support will be considered stable.

 2.  The upcoming  Xfce 4.10 will be still GTK-2 based. Midori is the primary web browser for the Xfce desktop environment. If Xfce 4.10 settings manager will be still with GTK-2 support and Midori will be using GTK-3, than configuring the GTK-3 theme/appearance/font hinting by editing some config files will be a hassle for Xfce users. I would really appreciate any hints on this.

So what concerns me: if Xfce is not migrating (yet), Midori is part of Xfce and GTK3 is not recommended (yet), what is the reason of this rush?

Thanks for your time.
Comment 3 Simone Scanzoni 2011-12-23 12:46:10 UTC
(In reply to comment #1)
> only temporarily... next version will not have gtk+-2.x ebuild anymore. get
> used to the gtk+-3.x migration. use theme that has both gtk+-2.x and gtk+-3.x
> support, such as greybird (x11-themes/greybird) or zukitwo
> (x11-themes/zukitwo).

Why? The author of this application still says (v. 0.4.3) that support for GTK+3 is beta quality and this is the only application in my system requesting GTK+3.
It seems a nonsense to me.
Is really the reason that one far day the world would use GTK+3 instead of 2? If XFCE 4.12 would take the same time 4.10 took it won't be out before 2013 and a lot of people (many who left GNOME3 for XFCE) would still use GTK+2 for more than a year.
At the moment the revbump to 0.4.3 would only need this:
mv midori-0.4.2-r200.ebuild midori-0.4.3-r200.ebuild
Why not?
Comment 4 Rafał Mużyło 2011-12-26 15:59:07 UTC
*** Bug 396055 has been marked as a duplicate of this bug. ***
Comment 5 Nesc 2011-12-26 18:31:23 UTC
In case of Midori of course that approach is just ridiculous as it really cuts off functionality (See duplicated bug adobe-flash doesn't work)
Comment 6 Rafał Mużyło 2011-12-27 16:05:30 UTC
(In reply to comment #5)
> In case of Midori of course that approach is just ridiculous as it really cuts
> off functionality (See duplicated bug adobe-flash doesn't work)

TBH, the only ridiculous part is that the upstream merged gtk3 parts before it was release ready.