<html>
<body>
At 07:42 AM 3/9/2016 -0500, Kyle Hall wrote:<br>
<blockquote type=cite class=cite 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?<br>
It seems like we're taking away one of the most powerful features of
Perl, it's extensive library of available modules.</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 class=cite cite>Just a thought.<br><br>
<a href="http://www.kylehall.info">http://www.kylehall.info</a><br>
ByWater Solutions (
<a href="http://bywatersolutions.com">http://bywatersolutions.com</a>
)<br>
Meadville Public Library ( <a href="http://www.meadvillelibrary.org">http://www.meadvillelibrary.org</a> )<br>
Crawford County Federated Library System ( <a href="http://www.ccfls.org">http://www.ccfls.org</a> )<br>
Mill Run Technology Solutions ( <a href="http://millruntech.com">http://millruntech.com</a> )<br><br>
On Tue, Mar 8, 2016 at 6:03 PM, Galen Charlton <<a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a>> wrote:<br>
<dl>
<dd>Hi,<br><br>
<dd>On Tue, Mar 8, 2016 at 12:50 PM, Brendan Gallagher <<a href="mailto:info@bywatersolutions.com">info@bywatersolutions.com</a>> wrote:<br>
<dd>Do we have a defined role description of responsibility of the Packaging Manager? </b>(I've only read Robin's posts to the mailing list before - is that it?)<br><br>
</dl><br>
We do now, seeded with my view of the position:<br><br>
<a href="https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager">https://wiki.koha-community.org/wiki/Project_roles#Packaging_manager</a>Â <br><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>
email: Â <a href="mailto:gmc@esilibrary.com">gmc@esilibrary.com</a><br>
direct: <a href="tel:%2B1%20770-709-5581">+1 770-709-5581</a><br>
cell: Â <a href="tel:%2B1%20404-984-4366">+1 404-984-4366</a><br>
skype: Â gmcharlt<br>
web: Â Â <a href="http://www.esilibrary.com/">http://www.esilibrary.com/</a><br>
Supporting Koha and Evergreen: <a href="http://koha-community.org">http://koha-community.org</a> & <a href="http://evergreen-ils.org/" eudora="autourl">http://evergreen-ils.org</a><br><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" eudora="autourl">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a><br><br>
<br>
_______________________________________________<br>
Koha-devel mailing list<br>
Koha-devel@lists.koha-community.org<br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" eudora="autourl">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" eudora="autourl">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" eudora="autourl">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" eudora="autourl">http://bugs.koha-community.org/</a> </blockquote>
<x-sigsep><p></x-sigsep>
---<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/" eudora="autourl">http://NavalMarineArchive.com</a>> and <<a href="http://ultramarine.ca/" eudora="autourl">http://UltraMarine.ca</a>><br>
</body>
</html>