Updated and rebased.
cc @etu @aanderse @Mic92

For which package(s) does ./configure: line 5836: /usr/bin/file: No such file or directory actually lead to a build error? Because I think I've seen that a whole bunch of times, but it always seemed like a harmless warning.

Only removed this warning. How this error affects the building I do not know.

@Izorkin Sorry, but I don't see the point of this PR if it actually doesn't fix any real error.

If we have a package that is broken due to this, it's worth doing. But this touch so many places to get rid of something that seems to be harmless...

@etu reakky merge this commit? - bb798c0

@Izorkin Since that commit only would add file as an additional dependency to the closure but not actually resolve any issue (that we know of)... I don't see the point of merging it.

I agree with @etu that we should be solving a known problem when we increase closure size, not appeasing a warning which has no known issue.

I would also point out that many packages mention a missing file executable, so conceivable this is an "issue" (or non issue) with 1 or more build systems. If this is an actual problem which requires solving we should look to solve it tree wide.