Oh man, FF4 is big! The PET package is 11.97MB, compare that with my FF 3.6.13 PET which is 9.16MB.
It is difficult to see what that 2.8MB extra bulk is offering, that FF3 doesn't have. Yes, support for HTML5, but FF4 is using the system libraries where possible, including system libvpx.
I don't know what to think...
Anyway, here is the PET (11.97MB):
Most important, if you want to try FF4 in Wary, you have to install the upgraded sqlite 3.7.5, pixman 0.18.4 and cairo 1.10.2, as explained in my previous post:
...they are also available at ibiblio.org.
...the next release of Wary will have these.
For developers, here is the .mozconfig file:
...it won't compile unless have --enable-jsd
# export MOZ_PHOENIX=1
# make -f client.mk
# cd objdir-fx-release
# make package
...makes tarball in objdir-fx-release/dist/
# cd ..
# make -f client.mk install
# ln -s firefox-4.0.1 /usr/lib/firefox
Comments:Posted on 16 May 2011, 7:19 by GCMartin
Seamonkey V2.1b1 to b3
Thanks for this Barry.
Will there be a SeaMonkey V2.1+ offering forthcoming for Wary was well at some point?
Posted on 16 May 2011, 7:24 by GCMartin
Seamonkey V2.1b1 to b3
Sorry, I think I see the dilemma from your prior blog. ....Cairo. If I understand, the 3 packages would need to be added to existing WARY, then the latest SM2.1+/FF4+ and all together, poses a larger WARY than would be desired.
Posted on 16 May 2011, 8:01 by BarryK
sqlite, pixman and cairo already exist in Wary, in fact in all puppies. I have just upgraded them. This has already been done, so the next Wary could be built with FF4 or SM2.1 if desired.
Yes, I will be compiling SM 2.1 sometime. I was planning on waiting until the final release of 2.1.
Posted on 16 May 2011, 19:52 by stiginge
+1 for SM 2.1. Seamonkey 1.18 just feels alittle outddated now!
Posted on 17 May 2011, 11:19 by ttuuxxx
Hi Barry I noticed you compiled it with ac_add_options --without-system-png
hmmm that would mean that it would use its own png and would give your build some bloat.
FF4 needs png to patched with apng for it to use the system png, http://sourceforge.net/projects/libpng-apng/ is where you can download the latest patch, so you could patch wary's default png lib+devx and update it.
Posted on 17 May 2011, 13:40 by technosaurus
apng (system png misleading)
In order to use system png, one must patch png with the animated png patches as mozilla does ... I don't think these patches were in t2 when the base was built, however it _shouldn't_ break anything to replace it.
Posted on 19 May 2011, 12:03 by happypuppy
Firefox 4 is big
"It is difficult to see what that 2.8MB extra bulk is offering, that FF3 doesn't have."
- Support for XRender and OpenGL HARDWARE ACCELERATION
- Mozilla's new HTML5 WEB AUDIO FRAMEWORK
Posted on 19 May 2011, 14:56 by BarryK
T2 has old libpng
Interestingly, the T2 people have stayed with the older libpng 1.2.x series, the latest they use is 1.2.44:
The T2 that I used to build Wary has libpng 1.2.40. The latest release of libpng is 1.5.2. The official libpng home has this to say:
libpng 1.2.x will continue to get security fixes for the foreseeable future
Official libpng home:
I have always compiling FF and SM with internal libpng. However, I see that the APNG site has a patch for libpng 1.2.44, so I will upgrade Wary from 1.2.40 to 1.2.44 and apply that patch.