<!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 14633 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 2<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: Koha 20.05.17 released (Victor Grousset/tuxayo)<br> 2. Re: Koha 20.05.17 released (Victor Grousset/tuxayo)<br> 3. Re: custom core patches management (Victor Grousset/tuxayo)<br> 4. Re: custom core patches management (Fridolin SOMERS)<br> 5. Re: custom core patches management (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 2 Nov 2021 21:55:13 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: Michael Kuhn <mik@adminkuhn.ch>,<br> koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Koha 20.05.17 released<br>Message-ID: <f22acd93-1538-17f7-aefb-cca7e69357de@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>On 21-11-02 09:42, Michael Kuhn wrote:<br>> This URL does not lead to the release notes. Can you please give us the <br>> correct URL?<br><br>Can you retry? It works for me even in private browsing so maybe someone <br>fixed it.<br><br>I usually check the link before sending the email but I missed this <br>time. Thanks for checking :)<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 2 Nov 2021 22:06:05 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: Michael Kuhn <mik@adminkuhn.ch>,<br> koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Koha 20.05.17 released<br>Message-ID: <488b5294-c920-7f0e-2e7b-efa7bce6b404@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>I had only saved the post as a draft, thanks Jonathan for publishing it.<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 3 Nov 2021 00:33:21 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: David Schmidt <mail@davidschmidt.at>,<br> Koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] custom core patches management<br>Message-ID: <08cef824-a49c-a7f9-e707-2285541820b4@tuxayo.net><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>How is your Koha installed? Debian packages?<br><br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 2 Nov 2021 14:27:33 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] custom core patches management<br>Message-ID: <a023eb12-2596-5fad-4248-8924b91a173a@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi,<br><br>Sounds like old-fashion version management :)<br><br>We use GIT versioning system https://git-scm.com.<br><br>The community real repository is <br>https://git.koha-community.org/Koha-community/Koha.git.<br>It is also on GitHub : https://github.com/Koha-Community/Koha<br><br>I suggest you create a GitHub account and fork it to propose your <br>changes (a new branch per feature).<br><br>Best regards,<br><br>Le 02/11/2021 à 00:00, David Schmidt a écrit :<br>> Hello koha community,<br>> <br>> We made some changes to our Koha instance and are now looking for a <br>> 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 <br>> compares Foobar.pm.orig with the installed file. if they match, the <br>> 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>> <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>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 5<br>Date: Wed, 3 Nov 2021 12:00:33 +1100<br>From: <dcook@prosentient.com.au><br>To: "'David Schmidt'" <mail@davidschmidt.at>,<br> <Koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] custom core patches management<br>Message-ID: <0ded01d7d04e$344850e0$9cd8f2a0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi David,<br><br> <br><br>I won’t make a comment on good vs bad strategies, as those are just subjective judgements, and ultimately it really all depends on your context.<br><br> <br><br>However, it sounds like you’re making a lot of work for yourself with those files. Using git commands, you could extract equivalents of those .orig, .changed, and .patched files. <br><br> <br><br>Also, by patching prod files like that, you don’t necessarily know exactly what your application state is at any particular time. I suppose you could probably do a git-based manual patching deployment system using git hashes to represent versions, but I’ve found in practice that those cause more headaches than they solve. <br><br> <br><br>Most Koha support providers (like the one I work for) will fork the branch(es) they want to customize, and then generate Debian packages which they distribute around the world as necessary. As soon as you’re running more than 1 Koha server, you really want a way to easily and quickly deploy changes across multiple machines. Koha is large and complex, so I think you’ll find that leveraging the work the community has done to build robust Debian packages is your best bet.<br><br> <br><br>Carrying customizations forward through time takes work, so it’s best to upstream everything you can, but I think we all know that’s not always feasible. Again git commands can help you show the changes you’ve made between different versions, and then you can make periodic efforts to review your customizations and port over anything you need to when a new version comes out. <br><br> <br><br>I hope that you find that helpful.<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of David Schmidt<br>Sent: Tuesday, 2 November 2021 9:01 PM<br>To: Koha-devel@lists.koha-community.org<br>Subject: [Koha-devel] custom core patches management<br><br> <br><br>Hello koha community,<br><br> <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> <br><br>- some of the changes are simply new files, thats easy.<br><br>- some changes were possible to put into plugins or use existing hooks.<br><br> <br><br>but how do you deal with changes to the koha sourcecode?<br><br> <br><br>this is our strategy:<br><br> <br><br>1) we have a git repo with our koha source code.<br><br>2) if we change code in Foobar.pm we create 3 files.<br><br>Foobar.pm.orig<br><br>Foobar.pm.changed<br><br>Foobar.pm.patch<br><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> <br><br>Does that sound like a good idea?<br><br>How do YOU manage core changes that do not go upstream?<br><br> <br><br>cheers,<br><br>david<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211103/c6d0d673/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 2<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>