I'm assuming Canonical wont remove it due to it "increasing customer synergies" or similar. Perhaps we make a package that patches this out? I'm thinking of so

I'm assuming Canonical wont remove it due to it "increasing customer synergies" or similar. Perhaps we make a package that patches this out? I'm thinking of something that detects this file and replaces it rather than a manual process. That way it gets fixed whenever "base-files" or whatever gets its updates. Make it a depend on base or similar. Somebody with a sharper set of teeth and specialised dorsal fin might want to do an audit for similar shenanigans. Canonical have "prior art" for this kind of thing. I doubt this is the only addition.