Summary: | net-www/mozilla-1.2.1-r5: ebuild stops when USE gtk2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sf <sf-gentoo> |
Component: | New packages | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sf
2003-03-04 04:20:05 UTC
Please read the bug report! It has nothing to do with bug #16466. az: since moz 1.2.x and up, i think GTK2 support has pretty much settled to a stable state ... Nope, many plugins do not work. He can export that in his /etc/profile if he really want it. Exporting what? WANT_GTK2="yes"? How should anyone know beforehand that there is a hidden mechanism to enable this particular build? Does everybody have to read release notes or somesuch for every package one is planning to emerge? Fact: the ebuild fails (<quote>!!! ERROR: net-www/mozilla-1.2.1-r5 failed.</quote>). Ergo: it is a BUG which should be fixed. you dont when it fails you go 'oh look, i need to do something ...' moz works great with GTK1, but you want GTK2 ... it has been known to compile fine but then have really crazy UI bugs ... this has spawned a ton of useless bug reports here on bugzilla ... so yes, GTK2 is getting better, but we dont want to handle bugs that we cant do anything about. hence, the 'you have to export a variable if you *reaaaaally* want GTK2' Fact: moz + GTK2 == extra bugs that waste Azarah's time Ergo: it will not be fixed |