prelink should not mess with running executables

[Garrett Holmstrom]

On 2012-07-19 15:57, Sam Varshavchik wrote:
> The fact that the same consequences can occur from
> upgrades, or some other unspecified events, is irrelevant, because
> appropriate measures /can/ be easily put in place, to take the
> appropriate action when upgrading, and most likely for whatever those
> other mysterious reasons might be. But this is not easily doable with
> prelink, without resorting to unwarranted nonsense, like inotify or
> similar workarounds.

Why is it simultaneously acceptable to put measures in place to deal 
with package replacement and unacceptable to put measures in place to 
deal with prelink when each of these methods of file modification has a 
well-documented and well-supported method of allowing you to react to them?

Technical reasons would be greatly preferred to value judgments.