Cross Reference: /external/chromium_org/net/tools/tld_cleanup/

When updating src/net/base/registry_controlled_domains/effective_tld_names.dat:

1. Obtain the new effective_tld_names.dat, probably by downloading
   http://goo.gl/Ji2bB

2. Remove whitespace from the ends of the lines.
   You could possibly use something like:
     sed -i -e "s/\s*$//g" \
         src/net/base/registry_controlled_domains/effective_tld_names.dat

3. Add the Chromium note back in just after the license at the top, and just
   before '===BEGIN ICANN DOMAINS==='. Ensure there is an empty line above and
   two empty lines below the note. The note should say:
// Chromium note: this is based on Mozilla's file:
//  http://mxr.mozilla.org/mozilla-central/source/netwerk/dns/effective_tld_names.dat?raw=1

4. Build tld_cleanup (the "(net)" > "tld_cleanup" project)

5. Run it (no arguments needed), typically from src/build/Release or
   src/build/Debug. It will re-generate
   src/net/base/registry_controlled_domains/effective_tld_names.gperf.

6. Check in the updated effective_tld_names.dat, effective_tld_names.gperf

Note that gperf is no longer used for effective_tld_names, but when building
chromium the file effective_tld_names.gperf will be parsed by make_dafsa.py
to generate the file effective_tld_names-inc.cc, which is included in
registry_controlled_domain.cc
Name	Date	Size
..	12-Mar-2015	4 KiB
BUILD.gn	12-Mar-2015	306
make_dafsa.py	12-Mar-2015	13.9 KiB
make_dafsa_unittest.py	12-Mar-2015	22.1 KiB
OWNERS	12-Mar-2015	17
PRESUBMIT.py	12-Mar-2015	1.1 KiB
README	12-Mar-2015	1.3 KiB
tld_cleanup.cc	12-Mar-2015	3.8 KiB
tld_cleanup.gyp	12-Mar-2015	524
tld_cleanup_util.cc	12-Mar-2015	8.9 KiB
tld_cleanup_util.h	12-Mar-2015	1.4 KiB
tld_cleanup_util_unittest.cc	12-Mar-2015	6.7 KiB