On Tue, Jul 15, 2008 at 02:54:50PM -0400, Brad wrote: > On Tuesday 15 July 2008 15:00:27 Martynas Venckus wrote: > > > From: Brad <[EMAIL PROTECTED]> > > > > > > On Tuesday 15 July 2008 13:42:19 Brandon Mercer wrote: > > > > On Tue, Jul 15, 2008 at 1:38 PM, Stuart Henderson <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > On 2008/07/15 13:07, Mike Erdely wrote: > > > > >> On Tue, Jul 15, 2008 at 04:37:13PM +0100, Edd wrote: > > > > >> > Whats the status of firefox 3 on OpenBSD? > > > > >> > > > > > >> > I have been using a package (given to me from viq, which i assume > > > > >> > is made from this patch), which has crashed once in about 3 days. > > > > >> > Thats about normal for firefox in my experience. > > > > >> > > > > > >> > I do notice a fair speedup. > > > > >> > > > > >> Like others, I see a fair speed up and I have only seen crashes with > > > > >> self-signed certificates. > > > > > > > > > > From some of the feedback I've heard, it doesn't entirely ready to > > > > > replace 2.x yet. I also note that upstream are not yet suggesting it > > > > > as an automatic upgrade for 2.x users. > > > > > > > > > > I wouldn't oppose having both versions in tree, but wouldn't be too > > > > > happy having 3.0 as the only Firefox version for the coming release. > > > > > > > > Agreed, the proper course should be to have both until the time comes > > > > to do away with 2.x > > > > Brandon > > > > > > IMO this is not realistic. We either stick with 2.x or go with 3.x, but > > > not create a mess with both. > > > > There's nothing wrong with having it in tree. > > > > I think the best way to handle this was suggested by pval, a while > > ago. Import it (www/mozilla-firefox3, or www/mozilla-firefox-devel), > > but not link to the builds yet. > > > > When we decide it's stable enough, reimport as www/mozilla-firefox. > > > > This would be easier both for me to work on further, and for people > > to test. > > Has anyone actually tested FF2 with newer NSPR/NSS to make sure there > are no compatability issues? FF2 builds fine with newer nspr/nss/sqlite3 on sparc64. Lightly tested.
Regards, Markus
