"Joshua Ferraro" <[EMAIL PROTECTED]> wrote:
> What ever happened to the idea of packaging Koha for one
> or more GNU/Linux distros (MJ, aren't you a Debian contributor?) ?
I'm a debian developer, if that's what you mean, but I've been stuck
doing most development on OSX for the last few months.
C
On Thu, Jul 24, 2008 at 8:45 PM, MJ Ray <[EMAIL PROTECTED]> wrote:
> Rick Welykochy <[EMAIL PROTECTED]> wrote:
>> Yes, the XML mess has bitten me before. It is probably something
>> beyond the scope of Koha installation to prevent.
>>
>> *UNLESS* perl and all its required C libs are plunked into
>>
MJ Ray wrote:
> Just to be as sure as we can be, shouldn't we bundle that perl and all
> its required C libs with copies of zebra, MySQL, Apache httpd, Linux
> and the tools needed to get it all running?
Actually, that is the only way to guarantee a working Koha install.
This is standard practice
Rick Welykochy <[EMAIL PROTECTED]> wrote:
> Yes, the XML mess has bitten me before. It is probably something
> beyond the scope of Koha installation to prevent.
>
> *UNLESS* perl and all its required C libs are plunked into
> a separate area and a known-to-be-right combination of
> everything perl
Joe Atzberger wrote:
> I agree the slippery
> XML parser is a likely culprit (and a serious pain), possibly because
> the "wrong" one is already pre-installed(?) for the OS.
Yes, the XML mess has bitten me before. It is probably something
beyond the scope of Koha installation to prevent.
*UNL
> Why would you deduce that it is the Perl CORE at fault?
I didn't: It's not my bug. The conclusion was that the 5.10 installation as
whole held some incompatibility. I agree the slippery XML parser is a
likely culprit (and a serious pain), possibly because the "wrong" one is
already pre-instal
Joe Atzberger wrote:
> what are the differences introduced at Perl 10.0
> in the CORE that you refer to? Would they affect an existing
> Koha/2.2.9 or Koha3.0 install?
>
>
> The cause/culprit isn't clear, but we definitely have compatibility
> issues between 5.10 and MARC::File::XML
>
> what are the differences introduced at Perl 10.0
> in the CORE that you refer to? Would they affect an existing
> Koha/2.2.9 or Koha3.0 install?
The cause/culprit isn't clear, but we definitely have compatibility issues
between 5.10 and MARC::File::XML, for example. See bug #2309:
http://bug
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
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
I think this idea is easy to do for a single target platform and harder to
do for heterogeneous platforms. For one thing you have current versions of
Ubuntu shipping with perl 5.10 (and its variations in core).
The available methods include:
- Bundle::Koha
- CPAN "autobundle"
- platform
On 2008/07/16, at 11:48 PM, Rick Welykochy wrote:
Chris Cormack 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?
Im su
Chris Cormack 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?
>>
> Im sure it could, you volunteering
>>
>> No CPAN. No failed makes. No mismatches.
>>
>> Can't the same be done for Koha?
>>
> Im sure it could, you volunteering Rick? :)
>
> Chris
This is a brilliant idea
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman
* Rick Welykochy ([EMAIL PROTECTED]) wrote:
> Hi Developers,
>
> I worked in an environment where a specific set of Perl packages
> known to work together well with everything else, i.e. database
> and web services, were required to create a virtual machine.
>
> We cobbled together perl + all per
Hi Developers,
I worked in an environment where a specific set of Perl packages
known to work together well with everything else, i.e. database
and web services, were required to create a virtual machine.
We cobbled together perl + all perl modules required.
The virtual builder then simply insta
18 matches
Mail list logo
