Have just one pefile.py in the tree |
|
Issue descriptionCurrently we have third_party/pefile via DEPS, and tools/symsrc/pefile.py checked in. tools/symsrc is git-mirrored and checked out on buildbots, so pefile.py should probably stay here. However, its pefile.py is older than the one in third_party. Proposal: 1. Update tools/symsrc/pefile.py to a newer version 2. Make scripts using third_party/pefile/pefile.py use the one in symsrc 3. Remove third_party/pefile from DEPS Please shout if that doesn't sound good to you :-)
,
Sep 5 2017
I think that we should just get rid of tools/symsrc entirely, the source indexing is now done via another script (in chrome/tools/symsrc/ in the internal repo) and most of this directory's content is old files that haven't been updated for a while. Last time I've checked we still wanted to keep these files here mostly for documentation purposes (i.e. this is how we do source indexing in Chrome), but I don't think that this is a valid argument (having these files confuses a lot of people and this copy is really outdated, it only supports SVN). We (apparently) also don't want to use them on the official bot for security reasons, hence the internal version. I'm not sure why these files get checked out on buildbots, but imho removing them and using only third_party/pefile is the right thing to do.
,
Sep 5 2017
tools/symsrc is definitely used to prepare .pd_ files for clang binaries that we upload to the symbol server.
,
Sep 5 2017
Ha, are you source-indexing these binaries?
,
Sep 5 2017
At the moment only symbol-indexing, here https://cs.chromium.org/chromium/src/tools/clang/scripts/package.py?q=package.py&sq=package:chromium&dr&l=131 That was added for bug 682500 . bug 700381 is about adding a source index too.
,
Sep 5 2017
Ha ok, what bothers me is that tools/symsrc/source_index.py is outdated* and should probably be removed to reduce the confusion. If we do this then tools/symsrc should probably be renamed tools/pe_utils as it's what it is. * The main difference is that this version supports SVN only, while the internal one is for Git only. |
|
►
Sign in to add a comment |
|
Comment 1 by thakis@chromium.org
, Sep 5 2017