https://rt-wiki.bestpractical.com/index.php?action=history&feed=atom&title=CustomizingWithPatches 2026-08-22T09:06:22Z Revision history for this page on the wiki MediaWiki 1.41.1 https://rt-wiki.bestpractical.com/index.php?title=CustomizingWithPatches&diff=758&oldid=prev 2016-04-06T20:03:38Z

<p>2 revisions imported</p> <p><b>New page</b></p><div>= Introduction =<br /> <br /> Patches (see some examples in [[Patches]]) are more local (than &#039;local&#039; customizations ;-).<br /> <br /> = Alternatives to patches =<br /> <br /> [[CustomizingWithLocalDir]] and [[CustomizingWithOverlays]].<br /> <br /> = Advantages of patches =<br /> <br /> First advantage is that you can group many changes in many files into one patch file. So a patch which adds one feature, which must be implemented in many modules can be hold in a single file together.<br /> <br /> If you&#039;re using the local dir then you have to check for changes in files that are overridden. Overlays are better as you have to check particular functions/methods only which should be easier. However, with patches you don&#039;t have to check anything as patches fail to apply if a source code has been changed dramatically on update.<br /> <br /> [[DirkPape]], for example, maintains a directory of patches and use a version upgrade script which automatically tries to apply the patches into a new version&#039;s source tree and reports conflicts.<br /> <br /> The second one reason to choose patches is better shareability, that&#039;s quite easy to read patches and they are smaller than copies of the same files with small changes.<br /> <br /> = Other ways to customize RT =<br /> <br /> [[Customizing]]</div>

Admin