GCC is the system compiler these days, CC should not be kept arround, especially not as a separate file. If any packages require CC, which they shouldn't, that will be a bug of these packages. Reproducible: Always
I see no benefit in removing it. Only breaks backwards compat for no gain. But letting toolchain maintainers close this one.
I see no reason to remove `cc`.
what mark said
What about hardlinking it? Not that I'd care, I'd rather want that useless file gone, but a hardlink wouldn't hurt, would it?
updating gcc-config to use hardlinks to its internal wrapper wouldn't be hard, but it would be dangerous imo. if someone were to modify any of the other binaries, it'd break all of them. we are talking about ~10KB of waste per wrapped binary. i would lean towards the existing behavior for safety since the overhead on disk isn't significant. having a specific target hardlink amongst themselves is probably fine, but they can't hardlink back to the original wrapper. file a new bug for this request.
