bin/clean.sh calls "git clean -Xdfq" for be/ and shell/. The reasoning behind using -X seems to be that we use the .gitignore file to specify build products in these folders. Thus, we remove all those known build products, but keep untracked artifacts around. I don't know a better way to do this, so I pushed a change to move the config file in question one level up in the directory structure: https://gerrit.cloudera.org/#/c/4850/
On Wed, Oct 26, 2016 at 11:25 AM, Jim Apple <jbap...@cloudera.com> wrote: > Which scripts use git clean -fdX? Which files in the .gitignore do you > think they need to delete to continue working properly? > > On Tue, Oct 25, 2016 at 5:58 PM, Lars Volker <l...@cloudera.com> wrote: > > My editor (vim) takes a config file in be/ (be/.ycm_extra_conf.py). I > > recently pushed a change <https://gerrit.cloudera.org/#/c/4562/> to > include > > it in the .gitignore file, making it survive runs of "git clean -fdx". > > However, I now found that we actually also call "git clean -fdX" > (uppercase > > X), effectively killing everything that is included in .gitignore from > > clean.sh. > > > > Is there a way to clean the repository while obeying the rules in > > .gitignore? Can we change the -x to a -X? Is there any other workaround > to > > retain this config file, short of linking it again every time I run > > clean.sh (or buildall)? > > > > Thanks for the help, Lars >
