Quote:
amigadave wrote:
So what is the usual solution to such a patch being provided by a (relatively) unknown source/developer?
As geit wrote, the usual process would be to read and understand the changed lines in the patch source and then check it for possible security or functionality flaws. Then, if the author of the original source has confidence, he will apply the patch and rebuild the binary.
So most of the work is not creating the new binary (easy task everyone can achieve by reading some general, not even morphos specific, documentation), but checking the source. This takes, depending on the size and complexity of the project and patch, quite some time. And as you might have guessed, a browser and his javascript engine is quite a complex application with tons of hard to predict side effects (which is what bugs and in particular security flaws are made of).
