Size of release tarballs

Hi, Lately there was a discovering about some files causing size growth of the release tarballs https://github.com/php/php-src/commit/469206c84e502e3e349655b802899d5e4d560f72 . Usually we strive to keep tarballs as small as possible and avoid disproportional growth of the size. This case seems to be of the exact nature. I would like to ask for an explicit response from RMs on this case. Perhaps it were also a good point to discuss a way to prevent big binary files to land in the repo. So far some files in the repo can be big. Where text or code can be then compressed just fine - images, sound and other binary stuff can't. So this means the simple way of checking the file size in the pre-commit hook might get complicated, as check of the mime types might likely need to be involved. It were good to hear some ideas on a possible solution and whether some explicit rule on this were worthwhile. Regards Anatol