search

aboutcode-org / deltacode

DeltaCode: compare two codebase scans (from ScanCode) to detect significant changes.
http://www.aboutcode.org/
20 stars 27 forks source link

Cloning repo on Windows 10 creates 'tcl' directory #10

Closed johnmhoran closed 6 years ago

johnmhoran commented 6 years ago

When the deltacode repo is cloned on Windows 10, followed by running ./configure.bat --clean and then ./configure.bat, a tcl directory appears after the the last step has finished. My local version of the former spats-deltacode repo does not contain a tcl directory, and I didn't encounter that directory during my previous work in spats-deltacode. After checking out a new branch and launching Visual Studio Code, VSCode indicates that there are 976 "pending changes" -- all of them evidently in this tcl directory.

My current resolution: I've deleted the tcl directory from inside my local branch.

steven-esser commented 6 years ago

@johnmhoran Can you do me a favor and clone https://www.github.com/nexb/conan

re-run those steps and see if you get the same thing; I initially took the configure scripts etc from there so could be an artifact of that.

Also, does this occur on a fresh clone of scancode as well?

steven-esser commented 6 years ago

Another question, does the tcl directory re-appear again after deletion and a run of?

$ ./configure.bat --clean
$ ./configure.bat
johnmhoran commented 6 years ago

@majurg The tcl directory is not present when I clone conan but appears after I run ./configure.bat.

Looking at my current dev scancode directory, it also contains a tcl directory. (Let me know if you'd still like me to run a fresh clone of scancode.)

From my local deltacode branch 9-refactor-generate-csv, I checked out develop, which no longer contains a tcl directory -- evidently deleting that directory from inside my local branch also removed it from the develop branch. I then ran ./configure.bat --clean and ./configure.bat, and the tcl directory reappeared.

steven-esser commented 6 years ago

@johnmhoran Looks like it is an artifact of the configure process for windows systems (possibly others).

Ive elected to simply add /tcl/ to our gitignore file, as it is in scancode-toolkit. It should no longer show up as an untracked directory and we can safely ignore it.

johnmhoran commented 6 years ago

Excellent. Thanks, @majurg .