answered
2016-10-21 12:56:00 +0200
nthn 12631 ●154 ●230 ●225
An example to show how patches work, and why they can't just stay active across Sailfish updates: let's say the original code in Sailfish is a sentence "There is a mouse in my house."
There is a patch that changes this sentence to "There is no mouse in my house, but there is a rat.", which changes the 3rd word of the sentence to "no", and adds ", but there is a rat" after the 7th word of the sentence and before the full stop (the 8th 'word' of the sentence).
A Sailfish update changes the sentence to say "There are mice in my house."
Now the patch, which changes the 3rd word and adds something in between 7 and 8, changes the sentence to "There are no in my house., but there is a rat"
As you can see, even though there was only a very small change in the original sentence, the new sentence is not correct anymore. Now imagine every word of the sentence is an instruction of some kind, and you'll see this could lead to a lot of trouble.
Because the patches do unmaintained stuff. The patches change files which are held in upstream packages of the distribution. If these files are changed (e. g. for other improvements) the patches will not work anymore. You patch on your own risk.
cy8aer ( 2016-10-21 10:29:52 +0200 )editBetter would be: Discussion Patch-specialists/Community <-> Jolla which patches would make sense for upstream.
cy8aer ( 2016-10-21 10:32:22 +0200 )editDiscussion Patch-specialists/Community sounds a good idea. (how to set those tags, then? sorry I'm a dummy)
danfin ( 2016-10-21 10:55:21 +0200 )editPatches is a modification to existing code. There is no magic in patches.
coderus ( 2016-10-21 11:57:21 +0200 )editPerhaps you should study the anatomy of a 'patch' and also how Patchmanager works with files, then learn how to author a patch and then you will see the answer to your own question and why things are currently the way they are.....annoying?, you should try being a maintainer! :D
Spam Hunter ( 2016-10-21 18:40:22 +0200 )edit