Home | History | Annotate | only in /external/chromium_org/net/tools/tld_cleanup
Up to higher level directory
NameDateSize
BUILD.gn04-Nov-2014306
make_dafsa.py04-Nov-201413.9K
make_dafsa_unittest.py04-Nov-201422.1K
OWNERS04-Nov-201417
PRESUBMIT.py04-Nov-20141.1K
README04-Nov-20141.3K
tld_cleanup.cc04-Nov-20143.8K
tld_cleanup.gyp04-Nov-2014524
tld_cleanup_util.cc04-Nov-20148.9K
tld_cleanup_util.h04-Nov-20141.4K
tld_cleanup_util_unittest.cc04-Nov-20146.7K

README

      1 When updating src/net/base/registry_controlled_domains/effective_tld_names.dat:
      2 
      3 1. Obtain the new effective_tld_names.dat, probably by downloading
      4    http://goo.gl/Ji2bB
      5 
      6 2. Remove whitespace from the ends of the lines.
      7    You could possibly use something like:
      8      sed -i -e "s/\s*$//g" \
      9          src/net/base/registry_controlled_domains/effective_tld_names.dat
     10 
     11 3. Add the Chromium note back in just after the license at the top, and just
     12    before '===BEGIN ICANN DOMAINS==='. Ensure there is an empty line above and
     13    two empty lines below the note. The note should say:
     14 // Chromium note: this is based on Mozilla's file:
     15 //  http://mxr.mozilla.org/mozilla-central/source/netwerk/dns/effective_tld_names.dat?raw=1
     16 
     17 4. Build tld_cleanup (the "(net)" > "tld_cleanup" project)
     18 
     19 5. Run it (no arguments needed), typically from src/build/Release or
     20    src/build/Debug. It will re-generate
     21    src/net/base/registry_controlled_domains/effective_tld_names.gperf.
     22 
     23 6. Check in the updated effective_tld_names.dat, effective_tld_names.gperf
     24 
     25 Note that gperf is no longer used for effective_tld_names, but when building
     26 chromium the file effective_tld_names.gperf will be parsed by make_dafsa.py
     27 to generate the file effective_tld_names-inc.cc, which is included in
     28 registry_controlled_domain.cc
     29