CLOBBER
author Jeff Walden <jwalden@mit.edu>
Mon, 19 Mar 2018 20:33:48 -0700
changeset 409136 1164d9b6127a233a251fc5cdcccd0204e0cef517
parent 407566 d6957f004e9cc3d7408ac3a8f2b49ff97556e27f
child 410366 10e682fef4a64676dad1dc922e8e6b22ccb9171e
permissions -rw-r--r--
Bug 1445524 - Always embed ICU data directly into the library, not storing it in a separate file in the file system. r=ted

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Historically updating ICU has required a CLOBBER.  Bug 1445524 is a fairly notable ICU-related change, so play it safe and force a full rebuild, even if no problem along these lines has actually been observed.