Summary: mozilla.dev.builds - October 14th to October 20th 2006

  • October 18th: Marcus is wondering about the Linux platform that is currently used to compile both public releases of Firefox and XulRunner.
  • On October 18th Marcus responded to his original post and expanded on the original content of his question.
Marcus claims that when he builds Firefox using CentOs he encounters crashes (segmentation faults) under Linux distributions such as gentoo, suse and fedora.
He also points out that when he performs a local build any of those platforms (gentoo, suse and fedora) he doesn't encounter any problems on the same machine.
  • Originally posted on Oct 19th: Christopher Finke is currently learning how to compile Firefox. Though he has succeeded in building Firefox he has so far failed to compile Firefox with his own extensions of choice so that his custom build would have those extensions enabled in the end product.
Christopher Finke is asking the community members for tutorials or any tips on how to get started.
He stated that he was able to pre-package the extensions that he wanted by following this walkthrough and a little bit of help from this post.
Christopher would not like to learn how to create a build of Firefox with custom extensions and not have those extensions appear in the Addons window.
  • On October 20th Jeff Walden responded Christopher Finke's question.
Jeff provided this link as an answer to Christopher Finkes' question.
  • Jan Vávra is wondering how he could create a win32 installer of Thunderbird that when executed, it would also install his extensions of choice.
He has already "studied" the makefiles but has had no success in achieving his goal.
Benjamin Smedberg mentioned in his post that Jan Vávra needs to add the extension files to the packaging manifest, which is used to create the installer.
In Jan Vávra's case he is modifying the Thunderbird installer so he needs to modify "mail/installer/windows/packages-static"


Sparky, the Linux performance test machine for the 1.8 branchs, is being decommissioned.
He also added that the Linux performance test data is now being provided by bl-bldlnx01.
Paul would like to hear from anyone who is against this decision.
He can be contacted via:
Email: preed@mozilla.com
IRC: preed on irc.mozilla.org
Phone: 650.903.0800 x256
  • On October 17th Benjamin Smedberg brought the following to the attention of the localizers and the build team:
That he is planning to upload the Firefox 2 language packages currently located at http://releases.mozilla.org/pub/mozi...rc3/win32/xpi/ to addons.mozilla.org in the next few days.
This will make the language packages available to everyone.
If you anyone has questions please feel free to ask Benjamin Smedberg.
You can do this by replying to the following post.


  • On October 19th J. Paul Reed posted the following discussion:
J. Paul Reed stated that he is also going to decommission comet, the machine that performed SeaMonkey Trunk gtk1 builds, this Friday.
J. Paul Reed's long-term goal is to remove old incompatible hardware.
  • On the same day Robert Kaiser responded to J. Paul Reed's post:
Robert Kaiser shared the following information about comet and btek machines:
  1. comet and btek are used as machines that upload nightly gtk1 builds.
  2. comet and btek are currently the fastest-cycling tinderboxes available therefore they are quite fast to detect general fires on the mozilla tree.
Robert Kaiser also suggested replacing luna, a machine used to create gtk1 builds, with a machine thats sole responsibility is to only the tests on builds from the official nightly machines.
  • On October 20th J. Paul Reed responded to Robert Kaiser's post:
J. Paul Reed replies to Robert Kaiser post and asks him to confirm the intention of his post.
J. Paul Reed also questions why gtk1 is still being built since it is know to be unsupported on trunk.
  • On October 20th Boris Zbarsky responded to J. Paul Reed previous post:
Boris Zbarsky answered J. Paul Reed's question that was posted in his previous reply.
J. Paul Reed had asked "why gtk1 was still being built".
Boris Zbarsky's said: The reason why gtk1 builds are still being performed is because: When requests are made to change build boxes to newer versions the people responsible for making the change reply with "That would require an OS upgrade".
  • On October 20th J. Paul Reed responded to Boris Zbarsky's post:
J. Paul Reed restates his overall goal that are
  1. "Getting us to not rely on hardware that you have to have in a certain position for it to boot"
  2. To use standard known configuration for every nightly build that is produced.
He also points out that there is a wiki page where the standard reference platform for Linux has been defined (for trunk builds).
  • On October 20th Boris Zbarsky responded to J. Paul Reed previous post:
In his post, Boris Zbarsky acknoleges the points that J. Paul Reed made in his previous post.


  • There were no meetings this week.

Summarized By: Vanessa Miranda & Mohammad Tirtashi