<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 14441 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 192, Issue 8<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: custom core patches management (David Schmidt)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 11 Nov 2021 09:11:03 +0100<br>From: "David Schmidt" <mail@davidschmidt.at><br>To: Koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] custom core patches management<br>Message-ID: <eb7b897c-a94a-4cb2-9ae4-92c48cf2e320@www.fastmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>we went along with our strategy and wrote a perl script that outputs a bash script.<br><br>After reviewing the output you can run the script and it will create the necessary symlinks and applies patches.<br><br>thats our short term approach, in the long run we might stop installing from koha debian packages and use the official koha git checkout directly and maintain branches for each koha instance.<br><br>if anyone is interested in the perl script I wrote let me know.<br><br>cheers<br>david<br><br><br>On Tue, 2 Nov 2021, at 11:00 AM, David Schmidt wrote:<br>> Hello koha community,<br>> <br>> We made some changes to our Koha instance and are now looking for a mechanism to apply them to a new installation.<br>> <br>> - some of the changes are simply new files, thats easy.<br>> - some changes were possible to put into plugins or use existing hooks.<br>> <br>> but how do you deal with changes to the koha sourcecode?<br>> <br>> this is our strategy:<br>> <br>> 1) we have a git repo with our koha source code.<br>> 2) if we change code in Foobar.pm we create 3 files.<br>> Foobar.pm.orig<br>> Foobar.pm.changed<br>> Foobar.pm.patch<br>> 3) on a new koha instance next we have a script `install.sh` that compares Foobar.pm.orig with the installed file. if they match, the patch is applied.<br>> <br>> Does that sound like a good idea?<br>> How do YOU manage core changes that do not go upstream?<br>> <br>> cheers,<br>> david<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211111/ac0691e4/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 192, Issue 8<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>