[yongjik]

I've been burnt by that convention pretty regularly:

(1) build automatically scans and adds all files in a directory

(2) I write a quick script foo.py in the directory to check something

(3) Boom, binary contains foo.py

I try to manually enumerate all files whenever I touch a build file.

[ungamedplayer]

A better solution is to a checkout of your build, then you wont have foo.py and you can be sure you haven't missed anything.

[yongjik]

That would work only if you always build after committing all your changes, which is IMHO another anti-pattern.

[ungamedplayer]

Er, but OP's tars up and ship after every change?

Get out of here with your antipatterns.