| Summary: | [gnome overlay] app-crypt/seahorse-plugins detects seamonkey gecko, fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexandre Rostovtsev (RETIRED) <tetromino> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | working seahorse-plugins-2.24.0.ebuild | ||
|
Description
Alexandre Rostovtsev (RETIRED)
2008-10-15 02:33:18 UTC
Created attachment 168502 [details]
working seahorse-plugins-2.24.0.ebuild
A working ebuild. Has 2 differences from what's currently in the Gnome overlay:
1. $(use_with epiphany gecko xulrunner) - to explicitly tell configure to look for xulrunner gecko (instead of seamonkey gecko, which would otherwise get detected first)
2. dependency on >=www-client/epiphany-2.24 - because earlier versions of epiphany could use either firefox or xulrunner, meaning one would need to add cumbersome logic to switch between --with-gecko=xulrunner and --with-gecko=firefox depending on how precisely epiphany was built. Since people using gnome-2.24 will presumably be using epiphany-2.24, it's easiest to get rid of the mess by requiring epiphany-2.24 (which is guaranteed to have been built against xulrunner).
(In reply to comment #1) > 2. dependency on >=www-client/epiphany-2.24 - because earlier versions of > epiphany could use either firefox or xulrunner, meaning one would need to add > cumbersome logic to switch between --with-gecko=xulrunner and > --with-gecko=firefox depending on how precisely epiphany was built. Since > people using gnome-2.24 will presumably be using epiphany-2.24, it's easiest to > get rid of the mess by requiring epiphany-2.24 (which is guaranteed to have > been built against xulrunner). > actually I plan to reintroduce epiphany with xulrunner 1.8 to the tree, unless someone tells me xulrunner 1.9 is going stable next week, I see no point in having to delay gnome stabilization due to xulrunner. Also please consider that ebuilds in overlay haven't been synced with the ones in portage which might explain some regressions as this one and this is because they haven't been re reviewed, by lack of time, to get the green light for portage. Thanks for reporting. fixed. please post a diff next time, easier to review. |