<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Sounds good to me.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>That’s a good point about Starman actually; Morbo/Hypnotoad are included with Mojolicious, but I suppose we don’t *<b>have</b>* to use Starman. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I was thinking too that at some point it would be nice to replace “unzip” with Archive::Zip, “xmlstartlet” with XML::LibXML, and pwgen with some other Perl replacement. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Actually, I wonder how far we should take it. Should “koha-core” really only depend on the Perl dependencies? Maybe some of the dependencies like pwgen, sudo, daemon, cron-daemon could be in a “koha-helpers” package as those are for the “koha-*” debian scripts rather than the “Koha” application per se. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>David Cook<o:p></o:p></p><p class=MsoNormal>Software Engineer<o:p></o:p></p><p class=MsoNormal>Prosentient Systems<o:p></o:p></p><p class=MsoNormal>72/330 Wattle St<o:p></o:p></p><p class=MsoNormal>Ultimo, NSW 2007<o:p></o:p></p><p class=MsoNormal>Australia<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Office: 02 9212 0899<o:p></o:p></p><p class=MsoNormal>Online: 02 8005 0595<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Tomas Cohen Arazi <tomascohen@gmail.com> <br><b>Sent:</b> Thursday, 15 October 2020 9:29 PM<br><b>To:</b> David Cook <dcook@prosentient.com.au><br><b>Cc:</b> Mason James <mtj@kohaaloha.com>; Jonathan Druart <jonathan.druart@bugs.koha-community.org>; koha-devel <koha-devel@lists.koha-community.org><br><b>Subject:</b> Re: [Koha-devel] Koha metapackage for easier installs<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I vote option 5.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I would love a way to install the 'core' dependencies in a self contained way, without external services. That would include Starman or whatever server implementation we use. And any 'external' service left outside this koha-core package.<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>El jue., 15 oct. 2020 a las 0:58, <<a href="mailto:dcook@prosentient.com.au">dcook@prosentient.com.au</a>> escribió:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>Oh yes I agree about Option 5 actually. (Except Starman as that's a Perl dependency which should actually be managed by cpanfile rather than debian/control.)<br><br>Strangely I didn't get Jonathan's email...<br><br>I have already added an update to <a href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26672" target="_blank">https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26672</a> but I'm happy to keep iterating on that one until we find just the right thing. <br><br>David Cook<br>Software Engineer<br>Prosentient Systems<br>72/330 Wattle St<br>Ultimo, NSW 2007<br>Australia<br><br>Office: 02 9212 0899<br>Online: 02 8005 0595<br><br>-----Original Message-----<br>From: Mason James <<a href="mailto:mtj@kohaaloha.com" target="_blank">mtj@kohaaloha.com</a>> <br>Sent: Thursday, 15 October 2020 2:50 PM<br>To: Jonathan Druart <<a href="mailto:jonathan.druart@bugs.koha-community.org" target="_blank">jonathan.druart@bugs.koha-community.org</a>>; David Cook <<a href="mailto:dcook@prosentient.com.au" target="_blank">dcook@prosentient.com.au</a>><br>Cc: koha-devel <<a href="mailto:koha-devel@lists.koha-community.org" target="_blank">koha-devel@lists.koha-community.org</a>><br>Subject: Re: [Koha-devel] Koha metapackage for easier installs<br><br>there is an option 5.<br><br>rather than koha-core being a metapackage which installs koha-common - koha-core is reduced version of koha-common, without apache2, memcached, zebra, elastic, starman, rabbitmq, etc...<br><br>this allows us to define koha-core as we need, without it inheriting all the dependencies of koha-common<br><br>i think option 4 will not work, because of the problem Jonathan described below<br><br><br>On 14/10/20 8:06 pm, Jonathan Druart wrote:<br>> koha-common is not koha-core, and that's the main problem<br>><br>> koha-common will pull apache2, memcached, zebra-2.0, starman<br>> (rabbitmq-server) which should not be in koha-core IMO.<br>><br>> Le mer. 14 oct. 2020 à 01:17,<<a href="mailto:dcook@prosentient.com.au" target="_blank">dcook@prosentient.com.au</a>> a écrit :<br>>> Hi all,<br>>><br>>><br>>><br>>> As we add external dependencies to Koha (e.g. MariaDB, Elasticsearch, RabbitMQ, etc), there are fears that we are making Koha harder to install for less technical users.<br>>><br>>><br>>><br>>> As a result, Jonathan, Tomas, Martin, Mason, and I have been discussing* creating a Koha metapackage that incudes all of Koha’s external dependencies, so that people can keep installing Koha with a minimum number of steps.<br>>><br>>><br>>><br>>> I think we’re at a point where we now need to decide on some names for metapackages.<br>>><br>>><br>>><br>>> Mason has already commented that it would be best to leave the current “koha” and “koha-common” packages as they are and I think that makes sense. While no one uses the “koha” package, I think there is still a dream of one day getting Koha into the upstream Debian repositories with that package name. Likewise, “koha-common” is so common that we had best not change it any time soon.<br>>><br>>><br>>><br>>> Here are some naming options that have been discussed:<br>>><br>>><br>>><br>>> Option 1<br>>><br>>> koha-lite (this metapackage installs koha-common) koha-full (this <br>>> metapackage installs koha-common, MariaDB, Elasticsearch, RabbitMQ, <br>>> etc)<br>>><br>>> Option 2<br>>><br>>> koha-full (this metapackage installs koha-common, MariaDB, <br>>> Elasticsearch, RabbitMQ, etc)<br>>><br>>> Option 3<br>>><br>>> koha-standalone (this metapackage installs koha-common, MariaDB, <br>>> Elasticsearch, RabbitMQ, etc)<br>>><br>>> Option 4 (David’s Preferred Option)<br>>><br>>> koha-core (this metapackage installs koha-common)<br>>><br>>> i. I would avoid “koha-lite” as it implies a little application whereas Koha is a large application<br>>><br>>> ii. I think that koha-common is currently misnamed as it really is more of a “core” package than a “common” package that is shared among different packages or standalone applications (like postgresql-common being shared between client and server). However, koha-common has legacy value as a name.<br>>><br>>> iii. In time, I’d like to see services like the SIP server, Z3950 responder, etc broken out of “koha-core” and put into their own packages. Eventually “koha-common” would just contain a set of core libraries that are shared amongst different Koha services. This would help with scalability, especially when using containers and other forms of modern computing.<br>>><br>>> koha-full (this metapackage installs koha-common, MariaDB, <br>>> Elasticsearch, RabbitMQ, etc)<br>>><br>>> i. I would avoid “koha-standalone” as I think that it implies a package without dependencies, whereas ours would have several dependencies and be more in line with “koha-full”. This is based on some searches through Debian repos:<br>>><br>>> <a href="https://packages.debian.org/search?suite=default§ion=all&arch=any" target="_blank">https://packages.debian.org/search?suite=default§ion=all&arch=any</a><br>>> &searchon=names&keywords=-standalone<br>>> <a href="https://packages.debian.org/search?searchon=names&keywords=-full" target="_blank">https://packages.debian.org/search?searchon=names&keywords=-full</a><br>>><br>>> ii. In Debian, there is a nginx-full package which installs many components (e.g. nginx-common, libnginx-mod-http-auth-pam, etc) and there is a nginx-core package which installs nginx-common and a small subset of libnginx-* packages<br>>><br>>><br>>><br>>> I ask that people comment here on the listserv, and ultimately we can conclude that discussion in Bugzilla athttps://<a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26672" target="_blank">bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26672</a>.<br>>><br>>><br>>><br>>> Cheers!<br>>><br>>><br>>><br>>> *based on my comment <br>>> athttps://<a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417#c26" target="_blank">bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417#c26</a><br>>> 6<br>>><br>>><br>>><br>>> David Cook<br>>><br>>> Software Engineer<br>>><br>>> Prosentient Systems<br>>><br>>> 72/330 Wattle St<br>>><br>>> Ultimo, NSW 2007<br>>><br>>> Australia<br>>><br>>><br>>><br>>> Office: 02 9212 0899<br>>><br>>> Online: 02 8005 0595<br>>><br>>><br>>><br>>> _______________________________________________<br>>> Koha-devel mailing list<br>>> <a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>>> <a href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>>> website :<a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a> git <br>>> :<a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a> bugs :<a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a><br>> _______________________________________________<br>> Koha-devel mailing list<br>> <a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>> <a href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>> website :<a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a> git <br>> :<a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a> bugs :<a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a><br><br><br><br>_______________________________________________<br>Koha-devel mailing list<br><a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br><a href="https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>website : <a href="http://www.koha-community.org/" target="_blank">http://www.koha-community.org/</a><br>git : <a href="http://git.koha-community.org/" target="_blank">http://git.koha-community.org/</a><br>bugs : <a href="http://bugs.koha-community.org/" target="_blank">http://bugs.koha-community.org/</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><div><div><p class=MsoNormal><span style='font-size:9.5pt'>Tomás Cohen Arazi<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.5pt'>Theke Solutions (<a href="http://theke.io/" target="_blank">http://theke.io</a>)<br></span><span style='font-size:9.5pt;font-family:"Segoe UI Symbol",sans-serif'>✆</span><span style='font-size:9.5pt'> +54 9351 3513384<br>GPG: B2F3C15F<o:p></o:p></span></p></div></div></div></div></div></div></body></html>