On Mon, 03 Mar 2008 04:48:13 -0500 Brett Goulder wrote:
Attached is a Firefox port 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, Swiftweasel [http://swiftweasel.tuxfamily.org/] already does that, iirc, so why not just package that?
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. With large disks these days, disk space is not that much of an issue.If several Mb saved this way are important to you, then, by all means, do it, but it's not worth the effort, unless in special/different circumstances, which do not apply here (again IMWHO :) ).
Start-time performance?Firefox startup is one-time event(start it up,use it, keep it open for a few days until it either chews large chunk of RAM or extensions need updating, then close/restart it). Anyway, if Mozilla's own binary builds are made that way, why just don't package and use them?Or Swiftweasel, for that matter? Or Debian's Iceweasel, debranded version? Crux philosophy is KISS, right?So why not do this in a simple, most elegant manner possible i.e in a way it was done so far? If you really want 'debloated' version of FF, use one of the alternatives above, and/or push alternative port to opt/contrib. Pedja -- If it looks like a troll, smells like a troll and quacks like a troll... ... kill it. It's a troll. - Mike Whitaker talking sense, in ukmg.