Joe Atzberger wrote:
> We do that for Koha's internal perl modules, and I think it makes sense
> there, but I would be very against doing it for *external*
> dependencies. It doesn't avoid entanglements with existing perl
> installations, because if you have 5.10 installed (e.g. Ubuntu) you
>
> One solution is to use a different location for the set of Perl
> modules used by Koha. This avoids any entanglements with existing
> Perl installations on the box. It is a very clean soln :)
>
We do that for Koha's internal perl modules, and I think it makes sense
there, but I would be very aga
Hi all,
The basic idea of this RFC is to add a translation mechanism for MARC
field, MARC subfield and System Preference's descriptions.
The mechanism would dynamically retrieve the description from a map
structure based on the user's currently selected language, which is not
possible at the m
MJ Ray wrote:
> Yes, and there are several ways to do it, including ones that I think
> are called PAR and PPM, but they should be able to build on the work
> we've done with Makefile.PL and they really need to be built on a
> stable release.
I will investigate PAR and PPM, whatever they are.
I h
Rick Welykochy <[EMAIL PROTECTED]> wrote: [...]
> We cobbled together perl + all perl modules required.
>
> The virtual builder then simply installed perl and all the
> perl modules we required.
>
> No CPAN. No failed makes. No mismatches.
>
> Can't the same be done for Koha?
Yes, and there are se
