<div dir="ltr">Thanks Paul! That raises an interesting question! That question being, should we be including Pure Perl libraries in our code base ( in some cases ). Our layout is a bit odd where we have our scripts and libraries sharing the same directory. In most projects we'd see our libraries in a "lib" directory. However, that is no technical reasons we couldn't include MARC::Frobnicate in the Koha codebase itself.<div><br></div><div>Pro: If the version of the library we use works, we know it will continue to work and will not be subject to regressions in newer versions</div><div>Con: We will need to update our libraries periodically</div><div><br></div><div>In essence, this is exactly what we do with our JavaScript libraries such as jQuery and DataTables.</div><div><br></div><div>Kyle</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>ByWater Solutions ( <a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a> )<br>Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a> )<br>Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br>Mill Run Technology Solutions ( <a href="http://millruntech.com" target="_blank">http://millruntech.com</a> )<br></div></div>
<br><div class="gmail_quote">On Wed, Mar 9, 2016 at 12:03 PM, Paul A <span dir="ltr"><<a href="mailto:paul.a@navalmarinearchive.com" target="_blank">paul.a@navalmarinearchive.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
At 07:42 AM 3/9/2016 -0500, Kyle Hall wrote:<br>
<blockquote type="cite">Also, are you saying any newly
packaged libraries *must* make it in to Debian? Can we not host our own
packaged libraries on our apt server? Why must packages meet the Debian
requirements?<br>
This seems like it's adding yet another barrier to entry for new Koha
developers. Now we all need to be Debian package maintainers as
well?<span class=""><br>
It seems like we're taking away one of the most powerful features of
Perl, it's extensive library of available modules.</span></blockquote><br>
One of Koha's strengths certainly was, and most probably still is, the
ability for an admin to be able to aptitude/apt-get (even yum)
dependencies that conform to her o/s. We used to publish
"warnings" about using CPAN. Debian trickles down to Ubuntu --
with a possible time-lag -- and these two o/s are perhaps the most used
by Koha-based libraries.<br><br>
If Koha needs to use a custom *library* and there is reticence to put it
through the Debian/Ubuntu loop, surely the proper solution is to put it
into the Koha environment (package and tarball) where it remains
Koha-specific and the remainder of the o/s, including Perl, stays
unchanged without potential repercussions on other installed
applications/progammes.<br><br>
This might well also facilitate version control -- each Koha update has
the correct libraries in /usr/share/koha/bin, /usr/share/koha/lib/C4,
wherever, but not in /usr/lib/perl* (or /usr/bin/perl) (with or without
/local/) available to the entire o/s.<br><br>
This removes any "barrier to entry for new Koha developers",
might ease proper installation/upgrade operations and has the potential
to obviate obscure security concerns.<br><br>
Best -- Paul<br><br>
<br>
<blockquote type="cite"><span class="">Just a thought.<br><br>
<a href="http://www.kylehall.info" target="_blank">http://www.kylehall.info</a><br>
ByWater Solutions (
<a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a>
)<br>
Meadville Public Library ( <a href="http://www.meadvillelibrary.org" target="_blank">http://www.meadvillelibrary.org</a> )<br>
Crawford County Federated Library System ( <a href="http://www.ccfls.org" target="_blank">http://www.ccfls.org</a> )<br>
Mill Run Technology Solutions ( <a href="http://millruntech.com" target="_blank">http://millruntech.com</a> )<br><br>
On Tue, Mar 8, 2016 at 6:03 PM, Galen Charlton <<a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>> wrote:<br>
</span><dl>
<dd>Hi,<br><br>
</dd><dd><span class="">On Tue, Mar 8, 2016 at 12:50 PM, Brendan Gallagher <<a href="mailto:info@bywatersolutions.com" target="_blank">info@bywatersolutions.com</a>> wrote:<br>
</span></dd><dd>Do we have a defined role description of responsibility of the Packaging Manager? (I've only read Robin's posts to the mailing list before - is that it?)<br><br>
</dd></dl><span class=""><br>
We do now, seeded with my view of the position:<br><br>
</span><a href="https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager" target="_blank">https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager</a>Â <br><span class=""><br>
On a side note, the overall page is new; I'm figuring that it might be a useful exercise to outline minimum role responsibilities for all of the named project positions.<br><br>
Regards,<br><br>
Galen<br>
-- <br>
Galen Charlton<br>
Infrastructure and Added Services Manager<br>
Equinox Software, Inc. / Open Your Library<br></span>
email: Â <a href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a><br>
direct: <a href="tel:%2B1%20770-709-5581" target="_blank">+1 770-709-5581</a><br>
cell: Â <a href="tel:%2B1%20404-984-4366" target="_blank">+1 404-984-4366</a><br>
skype: Â gmcharlt<br>
web: Â Â <a href="http://www.esilibrary.com/" target="_blank">http://www.esilibrary.com/</a><span class=""><br>
Supporting Koha and Evergreen: <a href="http://koha-community.org" target="_blank">http://koha-community.org</a> & <a href="http://evergreen-ils.org/" target="_blank">http://evergreen-ils.org</a><br><br></span><span class="">
_______________________________________________<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="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://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><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="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank">http://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> </span></blockquote>
<u></u><p><u></u>
---<br>
Maritime heritage and history, preservation and conservation, <br>
research and education through the written word and the arts.<br>
<<a href="http://navalmarinearchive.com/" target="_blank">http://NavalMarineArchive.com</a>> and <<a href="http://ultramarine.ca/" target="_blank">http://UltraMarine.ca</a>><br>
</p></div>
<br>_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a><br></blockquote></div><br></div>