On Mon, 03 Mar 2008 13:32:38 +0100 Clemens Koller wrote:
Brett Goulder schrieb:
Attached is a Firefox port
Hmm... didn't see any attachment here. :-(
Sorry, I was having some problems with my mail server and by the time I fixed it, I forgot to include the attachment. I sent a reply to the mailing list about it and also sent one with the attachment, but due to the size, it got delayed for moderator approval.
modified with all the changes I intend to push into the one in opt once 2.0.0.13 is released, mostly it's further debloating for Firefox, however it also includes one change that could potentially be disruptive to users: It links all of Firefox's internal libraries and extensions statically, into the main binary. This reduces disk space consumption, improves start-time performance and doesn't break any applications that build against Firefox. Mozilla's own binary builds are built this way, in fact.
That makes sense to me.
The reason this could be disruptive is because the final linking to generate the main firefox-bin file requires a lot of RAM, in my experience, 512MB minimum or a large amount of swap to compensate. This could cause build problems for some users, although Danny Rawlins managed to build this port on a system with only 256MB of RAM.
I was able to build opt/firefox on embedded PowerPC with 256MB successfully. But the build doesn't run. I haven't had time to have a closer look what's happening there and I didn't tests on x86 yet. All this needs to be fixed anyway.
I don't have a PowerPC system at my disposal, so I cannot offer any advice there. I'm mostly looking for testing on standard, x86 CRUX, but any testing is welcome.
I wanted to post this here to receive further testing before 2.0.0.13 is released, so that I don't push something potentially destructive to opt.
Push it again or put it in your repo. And please point out where to look closely for any problems.
It is currently in my personal repo, I don't intend to push anything to opt unless I know it works. As I mentioned, the primary thing I am looking for are problems resulting from linking the modified version due to low memory, if prevalent enough I won't merge those respective changes to opt, in order to avoid problems for users.
Regards,
Clemens
-- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc