Also as far as I'm aware there are no actual builds or any other factors involved in the patching, unless they somehow effect the hash of the original source : this is just debug output to go allow with the MD5.
This is just a find/replace string, it will produce identical output every time from identical input.
Without a new source hash (like from 1.4.5 -> 1.4.6, for example) there is no need to cater for different outputs of sw_vers.
The reason you have a different has is probably because the original PR that was merged was invalid, it should always produce the same hash for the same version of Mac OS or at least the same input hash of otool.
Also as far as I'm aware there are no actual builds or any other factors involved in the patching, unless they somehow effect the hash of the original source : this is just debug output to go allow with the MD5.
This is just a find/replace string, it will produce identical output every time from identical input. Without a new source hash (like from 1.4.5 -> 1.4.6, for example) there is no need to cater for different outputs of
sw_vers
.The reason you have a different has is probably because the original PR that was merged was invalid, it should always produce the same hash for the same version of Mac OS or at least the same input hash of otool.