Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 217003 - net-news/liferea doesn't disable gecko if xulrunner enabled
Summary: net-news/liferea doesn't disable gecko if xulrunner enabled
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Daniel Gryniewicz (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-09 10:02 UTC by Maxim Britov
Modified: 2008-04-10 18:32 UTC (History)
0 users

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 Maxim Britov 2008-04-09 10:02:14 UTC
net-news/liferea doesn't disable gecko if xulrunner enabled.
From current 1.4.14 ebuild:
 # we prefer xulrunner over firefox over seamonkey
 if use xulrunner ; then
         G2CONF="${G2CONF} --enable-xulrunner"
 elif use firefox ; then
         G2CONF="${G2CONF} --enable-gecko=firefox"
 elif use seamonkey ; then
         G2CONF="${G2CONF} --enable-gecko=seamonkey"
 else
         G2CONF="${G2CONF} --disable-gecko"
 fi

liferea enables gecko by default. With +xulrunner we doesn't provide --disable-gecko into configure.
It wrong for systems with FF3.

Reproducible: Always
Comment 1 Maxim Britov 2008-04-09 10:03:45 UTC
As workaround I have to use local ebuild with:
        # we prefer xulrunner over firefox over seamonkey
        if use xulrunner ; then
                G2CONF="${G2CONF} --enable-xulrunner"
        fi
        if use firefox ; then
                G2CONF="${G2CONF} --enable-gecko=firefox"
        elif use seamonkey ; then
                G2CONF="${G2CONF} --enable-gecko=seamonkey"
        else
                G2CONF="${G2CONF} --disable-gecko"
        fi
Comment 2 Daniel Gryniewicz (RETIRED) gentoo-dev 2008-04-09 13:19:58 UTC
I actually noticed this yesterday, when I was playing with webkit...

Anyway fixed in 1.4.14.  It will go stable in 30 days.
Comment 3 Maxim Britov 2008-04-09 13:51:25 UTC
1.4.14 from current portage tree still unfixed
and I have to patch local ebuild for my ~amd64.
Comment 4 Daniel Gryniewicz (RETIRED) gentoo-dev 2008-04-10 18:32:15 UTC
You didn't wait long enough for it to sync.  The version in the tree should be fixed.