Nate Gallaher wrote:
Vincent Povirk wrote:
It also seems to me that a --disable-gecko-downloader configure switch that would disable the dialog COMPLETELY (even "when needed") would put gecko on equal footing with optional library requirements. It would mean:
- You can warn about the perils of not having gecko at configure time.
- If gecko is installed properly, it's used properly, installed at
prefix creation time.
- If gecko is not installed properly, programs that need it will
simply fail, and you'll see an ERR in the console, as well as a nice "HTML rendering is disabled" message you wouldn't get from other components.
I would just like to second Vincent's suggestion.
+1 as well. Not all UNIXes have Gecko support packages built for them
James McKenzie
On Tue, Nov 17, 2009 at 10:27 PM, James Mckenzie <jjmckenzie51@earthlink.net
wrote:
+1 as well. Not all UNIXes have Gecko support packages built for them
+1 as well, I haven't tested the changes on OpenSolaris yet, but I plan to. :)
Tom
James McKenzie
Tom Wickline wrote:
On Tue, Nov 17, 2009 at 10:27 PM, James Mckenzie <jjmckenzie51@earthlink.net mailto:jjmckenzie51@earthlink.net> wrote:
> +1 as well. Not all UNIXes have Gecko support packages built for them
+1 as well, I haven't tested the changes on OpenSolaris yet, but I plan to. :)
Which makes -0 from both of you as you clearly don't understand the way Gecko package works. These are .dll files so they are only arch dependent from Wine point of view.
Jacek