Software Update:Nightly update infrastructure: Difference between revisions

Jump to navigation Jump to search
(fix up example, tweaks)
Line 12: Line 12:


The update channel is set to "default" (no updates) unless this line is in the mozconfig:
The update channel is set to "default" (no updates) unless this line is in the mozconfig:
  ac_add_options --enable-update-channel=nightly
  ac_add_options --enable-update-channel=nightly
For 1.5 the beta releases shipped with a "beta" channel, while the release candidates and final shipped with "release".
For 1.5 the beta releases shipped with a "beta" channel, while the release candidates and final shipped with "release".


To pull the code for complete update generation you need:
To pull the code for complete update generation you need:
  mk_add_options MOZ_CO_MODULE="mozilla/tools/update-packaging"
  mk_add_options MOZ_CO_MODULE="mozilla/tools/update-packaging"
This line is also used
 
This line is also used:
 
  ac_add_options --enable-update-packaging
  ac_add_options --enable-update-packaging
but it's not obvious why, because mbsdiff (the binary diff executable) is not required for a complete update, only mozilla/tools/update-packaging/{make_full_update.sh,common.sh}. (**CHECK**: Depends on trunk/branch ?)


The mar executable (mozilla/modules/libmar) is built by default.
This option ensures that the update-packaging and (m)bsdiff Makefile's are created. This is true for both the trunk and 1.8 branches.
 
The mar executable (mozilla/modules/libmar/tool) is built by default and copied into $objdir/dist/host/bin.
 
The (m)bsdiff executable creates binary diffs and is needed for partial updates only. It, too, is copied to $objdir/dist/host/bin.


==Snippet configuration==
==Snippet configuration==
Confirmed users
137

edits

Navigation menu