One of the things about releasing source code under various licenses is that it can’t be made purposely difficult to maintain: e.g. you can’t release obfuscated

One of the things about releasing source code under various licenses is that it can’t be made purposely difficult to maintain: e.g. you can’t release obfuscated garbage that “technically” compiles into the binary that you released, you must release the code that you actually maintain so any type of modification is feasible. Why doesn’t that also apply when there are rules about “removing” things? It could be extremely difficult to figure out all the places that specify something, especially if the wording is not absolutely consistent. I would hate to fix 99 of them and still be sued by missing the 100th. If a project wants to have a rule like this then they should say exactly how to comply. For example, don’t say “you must remove”; say “to replace the trademark, edit script_that_everything_uses_to_set_this”, or “here is the exhaustive list of files to change when replacing the trademark”, or whatever.